From: "Emilio Jesús Gallego Arias" <e@x80.org>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: Mailing List OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] LablGtk3 beta1
Date: Mon, 17 Dec 2018 13:11:27 +0100 [thread overview]
Message-ID: <87o99kmjyo.fsf@x80.org> (raw)
In-Reply-To: <AE4DDFB4-CB20-420C-A749-A0CCF69B7651@math.nagoya-u.ac.jp> (Jacques Garrigue's message of "Sun, 16 Dec 2018 17:12:13 +0900")
Jacques Garrigue <garrigue@math.nagoya-u.ac.jp> writes:
> 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.
Indeed, IMVHO lablgtk should follow the packaging structure hinted at
https://github.com/garrigue/lablgtk/pull/14 and don't depend on
`conf-gtk`.
This would have the important additional benefit of allowing fully
automatic OPAM releases, which are trickier to do when the conf-foo
package is there.
E.
next prev parent reply other threads:[~2018-12-17 12:11 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
2018-12-17 12:11 ` Emilio Jesús Gallego Arias [this message]
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=87o99kmjyo.fsf@x80.org \
--to=e@x80.org \
--cc=caml-list@inria.fr \
--cc=garrigue@math.nagoya-u.ac.jp \
/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