From: Chris Hecker <checker@d6.com>
To: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
Cc: Sven LUTHER <luther@dpt-info.u-strasbg.fr>,
Gerd Stolpmann <info@gerd-stolpmann.de>,
Pierre Weis <pierre.weis@inria.fr>,
caml-list@inria.fr
Subject: Re: [Caml-list] CDK with Ocaml 3.06 (fwd)
Date: Mon, 14 Oct 2002 22:25:51 -0700 [thread overview]
Message-ID: <4.3.2.7.2.20021014221300.0342f218@mail.d6.com> (raw)
In-Reply-To: <20021015051532.GB2224@iliana>
>Yes, that would be a good start, windows binaries and bytecode.
Yep, I think the right thing to do at the start would be to support windows
binaries, bytecode for those libraries that don't need external C code
libraries, and "opaque" source tarballs (by opaque, I mean the package
manager will fetch the source code tarball just like it will fetch the
binaries (and all the dependencies), but it won't attempt to build it or
make it work).
This would get the right stuff onto your machine, which is a start. Then
we publish some guidelines and slowly the source becomes more and more
consistent as people update, and then maybe we can solve the compilation
problem. But at least we'll have started.
>The outside dependencies (the ones on things not ocaml related, tcl/tk,
>gtk+ and so on) is the main difficulty here.
Yes. We just punt that problem for now.
>But the -pack option is not yet standardized, and not used in much
>cases, it seems to me.
It's brand new, so give it time (and we need to get it working on windows,
but that's close to solved now). Is there a problem with it that you're
implying, or just that it hasn't taken off yet?
> > Of course, if something like apt would just work for us (on all platforms,
> > source and binary), then that would be excellent and we should just start
> > using it.
>it will never just work, it 'just works' on debian, because of the
>debian maintainers who do the work of making sure the packages work.
No, I just meant could we use the apt executable and data formats and not
have to write any code that fetches files or checks dependencies and
whatnot? In other words, would it save time to try to use it, or is it
totally hard-coded to debian?
>I don't have time to work on this though :(((
Me neither, at least not for a year.
Chris
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-10-15 5:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 16:42 Alain Frisch
2002-10-14 17:39 ` Stefano Zacchiroli
2002-10-14 17:59 ` Alain Frisch
2002-10-14 18:16 ` Sven LUTHER
2002-10-14 20:38 ` Pierre Weis
2002-10-14 21:07 ` Sven LUTHER
2002-10-14 22:44 ` Gerd Stolpmann
2002-10-15 4:42 ` Sven LUTHER
2002-10-15 4:53 ` Chris Hecker
2002-10-15 5:15 ` Sven LUTHER
2002-10-15 5:25 ` Chris Hecker [this message]
2002-10-15 5:41 ` Sven LUTHER
2002-10-15 6:34 ` Chris Hecker
2002-10-15 5:02 ` Alessandro Baretta
2002-10-15 5:04 ` Chris Hecker
2002-10-15 5:08 ` Sven LUTHER
2002-10-17 17:57 ` Gleb N. Semenov
2002-10-15 11:21 ` Sign the packages (was Re: [Caml-list] CDK with Ocaml 3.06 (fwd)) Tim Freeman
2002-10-15 11:59 ` Sven Luther
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4.3.2.7.2.20021014221300.0342f218@mail.d6.com \
--to=checker@d6.com \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
--cc=luther@dpt-info.u-strasbg.fr \
--cc=pierre.weis@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).