From: oliver <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Build-/Installation-Tools - not enogh of them?
Date: Fri, 7 Dec 2018 16:19:48 +0100 [thread overview]
Message-ID: <20181207151948.5eyrbiolefu7tos5@first.in-berlin.de> (raw)
In-Reply-To: <CAP_800px5FLyeWf6p981CJftohc-B1say0Y=sJssnpt9LU77tw@mail.gmail.com>
Quoting Markus Mottl <markus.mottl@gmail.com> (snt: 2018-11-27 18:09 +0100 CET) (rcv: 2018-11-27 18:10 +0100 CET):
> On Tue, Nov 27, 2018 at 10:50 AM Oliver Bandel <oliver@first.in-berlin.de>
> wrote:
>
> > I'm happy with OCamlMakefile.
> >
>
> I have to say that I find it truly charming if not flattering that people
> are still using my ancient OCamlMakefile (which, btw., is now more than 20
> years old!).
[...]
Well, you use email here on the mailinglist.
It's much older than OCamlMakefile.
You still use it, even though there are a plenty of new possibilities in the web to talk about OCaml.
<iron>Maybe we should switch away from email then!</irony>
OCamlMakefile if fine for me: KISS principle.
If I would use come complex tools, I would provide a wrapping makefile to make default install easy.
Just for the record: I did not said, all the new tools are nonsense,
or would not help in certain projects.
I just asked those developers, who already worked into these tools,
to provide a way to make the build and install easy.
Especially if the sources of the project did not changed, or changed only minor,
switching to new build-/install-tools IMO does not make sense.
( -> never change a running install-prcedure nor change it's api )
But if one does this switch, providing the "make" / "make install" interface
for those, who had not the time to work into any new tool, would be easy.
By the way: I maintained ocaml-sqlite3 on AUR for Arch for a while.
At the moment I have not the time and nervs to look at dune, no matter
how good or bad it is.
So, I just disowned the ocaml-sqlite3 package on AUR.
Maybe someone will pick it up and provide a new version. Maybe not.
The package had 45 votes, which is comparingly much.
So there seems to be a need for this.
opam is part of the official Arch packages since a while,
so one could ask, why 45 people voted for the PKGBUILD-based package
instead of switching to opam.
(And there will be more users than the 45 who voted for it, I would guess.)
>
> Seriously, I think that every OCaml developer should switch to OPAM + Dune
> at this point.
Just because it's hype?
It's like: every technical discussion should be done via wh*tsapp, Sl*k, or foo or bar.
Email is so oldschool.
But of course people have different opinions on this.
OK, just ignore the 45 votes.
[...]
> I'm generally reluctant to jump on the
> next build tool or package manager,
Oh... so we are not far away here.
> but my expectation is that these tools
> will stay around for many years to come.
Heheh... maybe.
Ciao,
Oliver
next prev parent reply other threads:[~2018-12-07 15:19 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
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 ` oliver [this message]
2018-11-27 16:52 ` [Caml-list] " 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=20181207151948.5eyrbiolefu7tos5@first.in-berlin.de \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
/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