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 21:22:34 +0100 [thread overview]
Message-ID: <52A6268A.2070207@glondu.net> (raw)
In-Reply-To: <D26C180DCE9345F887B3C6645AA4CE3D@erratique.ch>
Le 09/12/2013 21:04, Daniel Bünzli a écrit :
>> You seem to forget all the system package managers (dpkg, rpm, ...).
>> While opam does have its advantages, it does not really compete with them.
>
> I don't forget them, I'm pretty sure the combination of opam/.install files can be used for automating the generation of such packages.
Yes, but the existing stuff too. And the packaging work is (should be)
mainly adding metadata and integrating with the other packages, which is
hardly automatable. What you are talking about is package building,
which can already be automated with the standard "./configure && make &&
sudo make install" interface.
>> http://xkcd.com/927/
>
> So what's your proposal then ?
I am not proposing anything new. You are.
Cheers,
--
Stéphane
next prev parent reply other threads:[~2013-12-09 20:22 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
2013-12-09 20:04 ` Daniel Bünzli
2013-12-09 20:22 ` Stéphane Glondu [this message]
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=52A6268A.2070207@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).