caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Stéphane Glondu" <steph@glondu.net>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Library installation procedure (for use with OPAM)?
Date: Mon, 09 Dec 2013 20:41:42 +0100	[thread overview]
Message-ID: <52A61CF6.50609@glondu.net> (raw)
In-Reply-To: <4F5AD22CADED45DBAD26A92D3F2B704D@erratique.ch>

Le 09/12/2013 18:37, Daniel Bünzli a écrit :
>> So, if everybody else have to implement them, opam's install files
>> become a new standard for the OCaml cummunity?
> 
> Frankly besides maybe wodi on windows I'm not so sure I see something
> reasonably competing with opam at that point, so that "everybody" may
> not include a lot of persons. Personally I don't have time to care
> for alternatives and I do what minimizes my admin/maintenance time at
> most.

You seem to forget all the system package managers (dpkg, rpm, ...).
While opam does have its advantages, it does not really compete with them.

>> Do most of us agree? (I'm not against it, I just don't want to rely
>> on 50 different standards).
> 
> I don't think it's a question of agreeing, usage will tell. Besides I
> don't see another standard, maybe `ocamlfind install` but it's
> limited in what it can install (and I hope that eventually the
> annoying two-headed structure ocamlfind/opam will disapear, e.g. the
> notion of ocamlfind package could be merged in the compiler).

The standard generic interface for package-manager-agnostic upstream
packages is:

  ./configure && make && sudo make install PREFIX=/foo

If people cannot agree on a standard implementation, at least they could
agree on the interface.

>> (A while ago, before opam, a new version of GODI broke on our main
>> platform because of some ocamlnet configuration bug, but I was able
>> to reinstall ocaml and about 25 third-party libraries and syntax
>> extensions from scratch without too much pain → we see great value
>> in that package-management independence)
> Why not. I guess you can see the value of having each of these
> libraries generating a .install file that you can process with a
> simple command line tool rather than have to deal with the
> idiosyncrasies of each custom (usually semi-broken) install
> procedure.

http://xkcd.com/927/


Cheers,

-- 
Stéphane



  reply	other threads:[~2013-12-09 19:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-08 20:55 Anthony Tavener
2013-12-09  9:23 ` Stéphane Glondu
2013-12-09 11:13 ` John Whitington
2013-12-09 15:04 ` Daniel Bünzli
2013-12-09 15:23   ` Sebastien Mondet
2013-12-09 15:57     ` Daniel Bünzli
2013-12-09 16:39       ` Sebastien Mondet
2013-12-09 17:37         ` Daniel Bünzli
2013-12-09 19:41           ` Stéphane Glondu [this message]
2013-12-09 20:04             ` Daniel Bünzli
2013-12-09 20:22               ` Stéphane Glondu
2013-12-09 21:04                 ` Daniel Bünzli
2013-12-09 21:36                   ` Anthony Tavener
2013-12-10  1:12                     ` Francois Berenger
2013-12-10 14:50       ` Daniel Bünzli
2013-12-10 16:49         ` [Caml-list] [ANN] opam-installer (beta) (was Re: Library installation procedure (for use with OPAM)?) Louis Gesbert

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=52A61CF6.50609@glondu.net \
    --to=steph@glondu.net \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    /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).