From: Pierre Weis <pierre.weis@inria.fr>
To: luther@dpt-info.u-strasbg.fr (Sven LUTHER)
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] CDK with Ocaml 3.06 (fwd)
Date: Mon, 14 Oct 2002 22:38:36 +0200 (MET DST) [thread overview]
Message-ID: <200210142038.WAA05623@pauillac.inria.fr> (raw)
In-Reply-To: <20021014181602.GA2620@iliana> from Sven LUTHER at "Oct 14, 102 08:16:02 pm"
[...]
> > 2) if we really need such a feature (for example just to have
> > transparent access to packages between different linux distributions
> > or between linux and windows and mac and ... worlds) who is
> > responsible to keep an archive of available package gettable via
> > ocamlfind or whatevere else?
> > CPAN, APT, and other approaches work because someon set up an
> > official or de-facto-official archive (Well, APT also support other
> > repositories, but official one are the most used and trusted ...).
>
> If this happens, maybe we can prevail on inria and the ocaml team to
> make disk space available to us ?
Yes, indeed. There is no problem of disk space here. The problem is to
grant access in a secure and reliable way.
> > 3) ocaml packages are usually distributed as source packages and we have
> > not a standardized way to build and install them, the success of
> > CPAN, APT, are due to the facts that _or_ the distribution is in
> > binary form with standardadized file system sructure _or_ the
> > distribution is in source form with standardized compilation and
> > installation procedure
>
> Yes, this is the problematic part.
I think we can set up a standardized compilation and installation
procedure (meaning a standard Makefile for libraries, based on the
configuration set up by the original Ocaml installation). We can start
with the Caml team maintained software (the ``bazaar'') and encourage
people to do the same for their own software by storing (and
distributing) it on our server. This could be a lot of book-keeping
but we could probably manage it...
Pierre Weis
INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://pauillac.inria.fr/~weis/
-------------------
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-14 20:38 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 [this message]
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
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=200210142038.WAA05623@pauillac.inria.fr \
--to=pierre.weis@inria.fr \
--cc=caml-list@inria.fr \
--cc=luther@dpt-info.u-strasbg.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