From: Francois Berenger <mlists@ligand.eu>
To: Malcolm Matalka <mmatalka@gmail.com>
Cc: Kakadu <kakadu.hafanana@gmail.com>,
jean-francois.monin@univ-grenoble-alpes.fr,
Caml List <caml-list@inria.fr>,
julia.lawall@lip6.fr, caml-list-request@inria.fr
Subject: Re: [Caml-list] Build-/Installation-Tools - not enough of them?
Date: Wed, 28 Nov 2018 10:52:57 +0900 [thread overview]
Message-ID: <bff20dae59fc5cbff486f773e6296278@ligand.eu> (raw)
In-Reply-To: <86tvk2d5ft.fsf@gmail.com>
On 27/11/2018 22:18, Malcolm Matalka wrote:
> Kakadu <kakadu.hafanana@gmail.com> writes:
>
>>> I fully second Julia.
>>> In order to teach OCaml, I need simple and clear instructions
>>> for students.
>>> The current situation is
>>> Search engine ->
>>> https://ocaml.org/docs/install.html ->
>>> https://opam.ocaml.org/doc/Install.html ->
>>> nightmare.
>>>
>>
>> +1. Installing Opam 2.0 on Ubuntu is even more complicated (The only
>> trick I know is adding avsm's PPA which is not easy to google)
>>
>> Happy hacking,
>> Kakadu
>
> I know at one point there was talk of opam2{rpm,pkg,deb} style tools.
> Does anyone know the status of those? I, personally, would benefit
> from
> an opam2freebsdports. ocaml-bundle came up earlier in the thread but
> as
> I said it feels stapled onto opam and doesn't use the opam env I've
> already setup (specifically pins + repos).
If you can build from sources, there is fpm that can create a deb or
rpm:
https://github.com/jordansissel/fpm
That's not a silver bullet, and it's not even specialized at ocaml
software/opam pacakges, but sometimes it helps.
> Maybe opam itself would benefit from a tool that could take a package
> and produce the package information in a format easily consumable by
> other languages so others can more easily write tooling around it?
> Heck, that information would make it easier to writes something in
> ocaml. I know this is one challenge I have, I *could* write some tools
> to make life easier but I don't have easy access to all the information
> in opam packages and poking around the opam libraries to build such a
> tool is too much effort for its priority for me.
next prev parent reply other threads:[~2018-11-28 1:52 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 10:14 [Caml-list] Build-/Installation-Tools - not enogh " 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 [this message]
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 ` [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=bff20dae59fc5cbff486f773e6296278@ligand.eu \
--to=mlists@ligand.eu \
--cc=caml-list-request@inria.fr \
--cc=caml-list@inria.fr \
--cc=jean-francois.monin@univ-grenoble-alpes.fr \
--cc=julia.lawall@lip6.fr \
--cc=kakadu.hafanana@gmail.com \
--cc=mmatalka@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