From: "Emilio Jesús Gallego Arias" <e@x80.org>
To: Francois Berenger <mlists@ligand.eu>
Cc: caml users <caml-list@inria.fr>, caml-list-request@inria.fr
Subject: Re: [Caml-list] LablGtk3 beta1
Date: Fri, 14 Dec 2018 12:38:00 +0100 [thread overview]
Message-ID: <87d0q4tk2v.fsf@x80.org> (raw)
In-Reply-To: <bb33b04ca2c710e8aa23ccdd52a33b7a@ligand.eu> (Francois Berenger's message of "Tue, 11 Dec 2018 12:09:37 +0900")
Hi Francois,
Francois Berenger <mlists@ligand.eu> writes:
> You are suggesting that opam should support the installation of
> different versions of the same thing.
> I think nix can do that, and that indeed looks like a current
> limitation of opam.
I wasn't going that far [as that tends to be quite complicated
technically].
I just proposed that our OPAM workflow should support for packages to
specify versioned dependencies on depext stuff, so a package A can do
"gtk-3.0 >= 3.12" and some other package B can specify "gtk-3.0 >=
3.14".
Even if that only serves as documentation for now.
The `conf-gtk` approach seems not very well suited for this.
E.
next prev parent reply other threads:[~2018-12-14 11:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 6:33 Jacques Garrigue
2018-12-06 10:05 ` Louis Gesbert
2018-12-06 10:35 ` Gabriel Scherer
2018-12-07 10:04 ` Emilio Jesús Gallego Arias
2018-12-07 10:25 ` Gabriel Scherer
2018-12-07 18:34 ` Emilio Jesús Gallego Arias
2018-12-11 3:09 ` Francois Berenger
2018-12-11 11:34 ` Louis Gesbert
2018-12-14 11:41 ` Emilio Jesús Gallego Arias
2018-12-14 11:38 ` Emilio Jesús Gallego Arias [this message]
2018-12-16 8:12 ` Jacques Garrigue
2018-12-17 12:11 ` Emilio Jesús Gallego Arias
2018-12-18 14:33 ` David Allsopp
2018-12-19 1:20 ` Emilio Jesús Gallego Arias
2018-12-19 10:15 ` David Allsopp
2018-12-19 11:13 ` Emilio Jesús Gallego Arias
2018-12-19 11:50 ` David Allsopp
2018-12-19 16:41 ` Emilio Jesús Gallego Arias
2018-12-20 11:33 ` David Allsopp
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=87d0q4tk2v.fsf@x80.org \
--to=e@x80.org \
--cc=caml-list-request@inria.fr \
--cc=caml-list@inria.fr \
--cc=mlists@ligand.eu \
/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