caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: "Stéphane Glondu" <steph@glondu.net>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Build-/Installation-Tools - not enogh of them?
Date: Sat, 8 Dec 2018 01:58:30 +0100	[thread overview]
Message-ID: <etPan.5c0b1736.b0aa6a4.a9b0@erratique.ch> (raw)
In-Reply-To: <947dc3fd-50b3-28d4-c72e-64efc3d6f8de@glondu.net>

 On 7 December 2018 at 14:22:06, Stéphane Glondu (steph@glondu.net) wrote:

> If everybody had agreed on a single language, we wouldn't need all these
> language specific package managers either :-) Replace "language" by
> "operating system" or "platform" or ...

This comparison is entirely inadequate. Distribution tarballs are distribution tarballs. The fact that linux distros/bsds/whatever are not even able to agree on a single name and version number for the same tarballs and that we need to lose our time to maintain mappings on how each random distribution names the same fucking software artefact should be a hint that this is *not* about agreeing on a single language and platform but rather a problem in consistent human stupidity.

> Each package manager has its own set of features ("developer
> friendly"-ness is just a matter of taste IMHO)... You sound like system
> package managers have no features, but the example you give
> ("distinguish what you want to compile a project from what you want for
> your system") is supported by the Debian toolchain (and I guess others).

This obsession about features is quite interesting, always this myth about the more features the better... Maybe opam does only the 5% of your truly awesome system package managers but it does so in a relatively lean way, that is adequate for development and allows to define and maintain (at the risk of repeating myself) packages universes accross your pet distribution and/or operating system. 

You are all most welcome to live in your distro and package manager bubbles and idiosyncrasies but don't start claiming they are able to provide what opam and OCaml opam repository currently provide because they simply do not.

> I haven't been very much impressed by opam (I mean, the package manager
> itself) so far, actually there are basic features that are missing (or
> not obvious) in opam (such as redistributable binary packages).

Opam is far from perfect and I have many concerns about its current usability. But the basic feature you mention is missing is absolutely unuseful to solve the problem opam is solving right now (see above in case that is still not clear).

> I don't believe the existence of a "single package manager" as you hypothesized would
> have prevented the proliferation of language specific package managers.

I gave one explanation, I don't claim that this is it, but at least provide a competing one. So far you did not so maybe you should try to reflect a bit more on the problem. I don't think anyone here would be sad to see language specific package managers go and frankly I'm pretty sure both opam developers and opam repository maintainers would be glad to spend their time on more fun projects.

Best,

Daniel


 

-- 
Caml-list mailing list.  Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list https://inbox.ocaml.org/caml-list
Forum: https://discuss.ocaml.org/
Bug reports: http://caml.inria.fr/bin/caml-bugs

  reply	other threads:[~2018-12-08  0:58 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 10:14 Oliver Bandel
2018-11-26 16:41 ` Yawar Amin
2018-11-26 16:57   ` Julia Lawall
2018-11-26 17:15     ` Yawar Amin
2018-11-26 20:33       ` Julia Lawall
2018-11-26 20:47         ` Yawar Amin
2018-11-26 20:54           ` Julia Lawall
2018-11-26 21:19             ` Yawar Amin
2018-11-26 21:29               ` Julia Lawall
2018-11-26 22:16                 ` SP
2018-11-27  5:24                   ` Malcolm Matalka
2018-11-28  0:20                     ` SP
2018-11-27  6:11                   ` Julia Lawall
2018-11-27  8:45                     ` SF Markus Elfring
2018-11-28  0:04                     ` SP
2018-11-27  9:27                 ` SF Markus Elfring
2018-11-27 10:08                   ` Julia Lawall
2018-11-27 10:28                     ` [Caml-list] Build-/Installation-Tools - not enough " SF Markus Elfring
2018-11-27 10:34                       ` Julia Lawall
2018-11-27 11:05                         ` Jean-Francois Monin
2018-11-27 11:00                           ` Kakadu
2018-11-27 13:18                             ` Malcolm Matalka
2018-11-28  1:52                               ` Francois Berenger
2018-11-28 15:21                             ` Ian Zimmerman
2018-11-27 13:07                     ` [Caml-list] Build-/Installation-Tools - not enogh " Jean-Marc Alliot
2018-12-06 12:21               ` Richard W.M. Jones
2018-12-06 16:10                 ` Yawar Amin
2018-12-06 20:18                   ` Richard W.M. Jones
2018-12-07  7:31                     ` Daniel Bünzli
2018-12-07  7:44                       ` [Caml-list] What happened to the 'ancient' library for OCaml? Francois Berenger
2018-12-07  8:24                         ` Richard W.M. Jones
2018-12-07  8:26                       ` [Caml-list] Build-/Installation-Tools - not enogh of them? Richard W.M. Jones
2018-12-07  9:01                         ` Daniel Bünzli
2018-12-07 13:22                       ` Stéphane Glondu
2018-12-08  0:58                         ` Daniel Bünzli [this message]
2018-12-13 23:45                           ` SP
2018-12-11  2:47                         ` Francois Berenger
2018-12-07 13:12                     ` Malcolm Matalka
2018-11-27 14:32             ` Anil Madhavapeddy
2018-11-27 14:35     ` Gerd Stolpmann
2018-11-30 15:23   ` Louis Gesbert
2018-11-26 22:44 ` Jaap Boender
2018-11-26 22:55   ` Simon Cruanes
2018-11-27 13:29     ` Oliver Bandel
2018-11-27 13:45       ` [Caml-list] Build-/Installation tools - not enough " SF Markus Elfring
2018-11-27 15:06       ` [Caml-list] Build-/Installation-Tools - not enogh " Simon Cruanes
2018-11-27 15:49         ` Oliver Bandel
2018-11-27 16:27           ` Daniel Bünzli
2018-11-27 17:46             ` Jaap Boender
2018-11-28 11:47               ` Jeremie Dimino
2018-12-01 15:12                 ` [Caml-list] How to start with the curren toolset? Hendrik Boom
2018-12-01 16:56                   ` Ian Zimmerman
2018-12-02 15:27                   ` Daniel Bünzli
2018-12-02 23:36                     ` David Allsopp
2018-12-03  2:19                     ` [Caml-list] let's give a try at opam-bundle Francois Berenger
2018-12-02 17:44                   ` [Caml-list] confusing message in opam installer Hendrik Boom
2018-12-02 17:50                     ` Julia Lawall
2018-12-05 19:07                       ` Raja Boujbel - OCamlPro
2018-11-27 16:27           ` [Caml-list] Build-/Installation tools - not enough of them? SF Markus Elfring
2018-11-27 17:09           ` [Caml-list] Build-/Installation-Tools - not enogh " Markus Mottl
2018-11-30 12:41             ` [Caml-list] <DKIM> " Vu Ngoc San
2018-12-07 15:19             ` [Caml-list] " oliver
2018-11-27 16:52       ` Hendrik Boom
2018-11-27 14:11     ` Jaap Boender
2018-11-27  2:33   ` Francois Berenger
2018-11-27 13:31     ` Oliver Bandel
2018-11-27 13:40 ` John F Carr
2018-11-30 16:31   ` Louis Gesbert
2018-12-01  5:01     ` Louis Roché
2018-12-03  0:16     ` Edwin Török

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=etPan.5c0b1736.b0aa6a4.a9b0@erratique.ch \
    --to=daniel.buenzli@erratique.ch \
    --cc=caml-list@inria.fr \
    --cc=steph@glondu.net \
    /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).