From: Markus Mottl <markus.mottl@gmail.com>
To: Paolo Donadeo <p.donadeo@gmail.com>
Cc: OCaml mailing list <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml Labs
Date: Sat, 20 Oct 2012 16:08:56 -0400 [thread overview]
Message-ID: <CAP_800qkQ8E-w2OU8q9fDvJHc7k0r6cW1nf+n2xDjjHp7vSA5Q@mail.gmail.com> (raw)
In-Reply-To: <CAPzAKVCOC0Y_gS6kx3bmf-93SSSTsSnWvSA6dSFWTJznsGa1Zg@mail.gmail.com>
On Sat, Oct 20, 2012 at 1:31 PM, Paolo Donadeo <p.donadeo@gmail.com> wrote:
> Do we really need of yet another package manager? How can't OPAM scatter the
> community further?
Why should another package manager scatter the community? If a new
package manager turned out to be worse than existing ones, nobody
would use it. If it turned out to be better, why should having this
alternative be a bad thing?
I have so far been quite pleased with OPAM. In my opinion it makes
life easier for both package users and contributors than other
existing approaches I have tried so far. It's no surprise that it
already offers an impressive range of packages at this early stage.
My feeling is it will have a great future and has the potential to
become the standard packaging tool for managing OCaml installations.
> Now, if I write a small library and I want to make it available to OCaml
> developers, I have to care about: making the source code Debian and Red Hat
> friendly, godi friendly, oasis-db friendly and, now, OPAM. And there are
> probably other systems I don't even know.
I don't really care about specifically supporting binary
distributions, since I'm not targeting one particular platform (Linux)
anyway. Binary packagers will contact you (the developer) if there is
any sort of awkwardness about your configure/build/install process,
which happens exceedingly rarely anyway.
The problems I had with Godi were not so much with how to distribute
my sources, but the elaborate and error-prone process required to
release Godi packages. Being Oasis-DB friendly means, I guess, simply
using Oasis for package specification. This specification is
generally useful, also for releasing to other package managers, and
doesn't just support Oasis-DB.
> It's not a critics or a rant, but honestly I need a compass to orient myself
> in the jungle of package managers for OCaml, and I'm using OCaml since
> years, think about a novice...
To me personally OCaml package management tools have not been
particularly satisfactory for years. OPAM is a fresh if not to say
refreshing approach. If OPAM had been available to me when I was a
novice, it would have made my first OCaml experience so much better.
Regards,
Markus
--
Markus Mottl http://www.ocaml.info markus.mottl@gmail.com
next prev parent reply other threads:[~2012-10-20 20:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 1:46 Yaron Minsky
2012-10-20 17:31 ` Paolo Donadeo
2012-10-20 19:34 ` Adrien
2012-10-20 20:08 ` Markus Mottl [this message]
2012-10-20 21:10 ` Anil Madhavapeddy
2012-10-20 23:38 ` Paolo Donadeo
2012-10-21 5:42 ` Fabrice Le Fessant
2012-10-23 1:44 ` Francois Berenger
2012-10-21 8:03 ` Ralf Treinen
2012-10-22 10:56 ` David Rajchenbach-Teller
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=CAP_800qkQ8E-w2OU8q9fDvJHc7k0r6cW1nf+n2xDjjHp7vSA5Q@mail.gmail.com \
--to=markus.mottl@gmail.com \
--cc=caml-list@inria.fr \
--cc=p.donadeo@gmail.com \
/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