caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Chris Hecker <checker@d6.com>
To: Sven LUTHER <luther@dpt-info.u-strasbg.fr>,
	Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: Sven LUTHER <luther@dpt-info.u-strasbg.fr>,
	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 21:53:05 -0700	[thread overview]
Message-ID: <4.3.2.7.2.20021014214720.0320a448@mail.d6.com> (raw)
In-Reply-To: <20021015044203.GA1016@iliana>


>At least for the windows solution, i strongly think a binary
>distribution mechanism is what is needed for the users and also would
>save a lot of time and 'howto build' kind of questions on the mailing
>lists. There is no reason not to do so, i am no windows expert, but
>windows offer a stable set of libraries and other system component that
>can be relied upon to install ocaml binary packages upon. This already
>works for ocaml itself.

Yes, binary distribution would work fine on windows.  Bytecode binary 
distribution for most libraries should work fine on all platforms.

I think at this point it's more important to do something small and get it 
going than it is to solve all possible package management problems.  Even 
something that just allowed a standard way of getting a tar ball of source 
for a given package and for its dependencies would be better than nothing, 
and we could improve it as we went.

The -pack option made this a lot simpler, because now libraries can be 
distributed as a single module.  If we make some relatively simple 
standards for build targets I think we can start making progress.

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.

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


  reply	other threads:[~2002-10-15  4:53 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 [this message]
2002-10-15  5:15               ` Sven LUTHER
2002-10-15  5:25                 ` Chris Hecker
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.20021014214720.0320a448@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).