Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Alain Frisch <frisch@clipper.ens.fr>
To: Stefano Zacchiroli <zack@cs.unibo.it>
Cc: Caml list <caml-list@inria.fr>
Subject: Re: [Caml-list] CDK with Ocaml 3.06 (fwd)
Date: Mon, 14 Oct 2002 19:59:51 +0200 (MET DST)	[thread overview]
Message-ID: <Pine.SOL.4.44.0210141944010.16561-100000@clipper.ens.fr> (raw)
In-Reply-To: <20021014173931.GD10510@cs.unibo.it>

On Mon, 14 Oct 2002, Stefano Zacchiroli wrote:

> 1) does we really need such a feature, aren't distribution born for such
>    issues? (obviously I'm thinking about the Linux world here)

Well, Linux is not the center of the world (even of the Unix-world). There
are several OS, several distributions, and you're not always sys admin on
the system you're working on (or don't want to use root priveleges to
install an ocaml package).


> 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 ...).

What about a Central OCaml Archive (with a nice acronym; or simply a
centralized list of URLs) and some conventions about namespaces ?

If it is impossible to manage such a central repository, an intermediate
solution would be to provide explicitly URLs for findlib-dependencies.

> 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

A standardized compilation and installation procedure would be great,
indeed.

-------------------
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-14 17:59 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 [this message]
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
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=Pine.SOL.4.44.0210141944010.16561-100000@clipper.ens.fr \
    --to=frisch@clipper.ens.fr \
    --cc=caml-list@inria.fr \
    --cc=zack@cs.unibo.it \
    /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