caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: "Emilio Jesús Gallego Arias" <e@x80.org>
Cc: Mailing List OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] LablGtk3 beta1
Date: Sun, 16 Dec 2018 17:12:13 +0900	[thread overview]
Message-ID: <AE4DDFB4-CB20-420C-A749-A0CCF69B7651@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <87d0q4tk2v.fsf@x80.org>

2018/12/14 20:38, Emilio Jesús Gallego Arias <e@x80.org>:
> 
> 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.

Emilio, I do agree with you on that.
I added a conf-gtk3 as was suggested to me, and since lablgtk3 requires
gtk 3.18, if dependes on a versioned package conf-gtk3.18 (i.e. cong-gtk3 ">= 18”)
However, if somebody else introduces a conf-gtk3.22 version, that one will
be installed by default (even for lablgtk3), and fail if one gtk-3.18 is available,
so this does not seem to be the right solution for versioning, and I see no
other way to do it with the current opam.

Jacques


-- 
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-16  8:12 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
2018-12-16  8:12           ` Jacques Garrigue [this message]
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=AE4DDFB4-CB20-420C-A749-A0CCF69B7651@math.nagoya-u.ac.jp \
    --to=garrigue@math.nagoya-u.ac.jp \
    --cc=caml-list@inria.fr \
    --cc=e@x80.org \
    /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).