From: Gabriel Scherer <gabriel.scherer@inria.fr>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] LablGtk3 beta1
Date: Thu, 6 Dec 2018 11:35:20 +0100 [thread overview]
Message-ID: <CAPFanBGcnTaHAaenFGjyD2Kq_XN7fg-VK=j-WAn7hESjfVJGKw@mail.gmail.com> (raw)
In-Reply-To: <966B3CBE-29BB-4336-BDBF-0012723E7099@math.nagoya-u.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 3475 bytes --]
> There is no opam package yet, because I’m not sure how to do that:
> I seem to need to add a new conf-gtksourceview3 package too, and I’m not
> sure how to proceed. Help accepted.
The point of conf-* packages is to centralize the logic to check for an
outside-opam dependency (that must be provided by the operating system); if
an installation task fails on a conf-* target, the user should know that
the problem is not their OCaml environment, but a system dependency to
install. Each conf-* package implements its own
external-dependency-detection logic; some packages call pkg-config to check
that a library exist, or even try to build a dummy C program with the
library, but the least they can be expected to do is to check for a list of
"depexts", system packages (one for each distribution / OS package manager)
that contain the dependency.
For conf-gtksourceview3, you should aim to do no worse than
conf-gtksourceview2. The source fo that package can be looked in the
current opam-repository:
https://github.com/ocaml/opam-repository/blob/master/packages/conf-gtksourceview/conf-gtksourceview.2/opam
You can see in the source that it lists some depexts, and also performs a
pkg-config test in its `build` rule.
It should be very easy to port that package into a conf-gtksourceview3
package, replacing what needs to be replaced:
- are the licence and homepage the same?
- what is the name of the pkg-config argument you should pass?
(I just checked, it is "gtksourceview-3.0")
- what are the name for the gtk3 versions of the system packages?
You can search the web to find the name of a package for a given
distribution,
and the links to do this are listed in
https://github.com/ocaml/opam-depext/blob/master/README.md
On Thu, Dec 6, 2018 at 7:33 AM Jacques Garrigue <
garrigue@math.nagoya-u.ac.jp> wrote:
> Dear LablGtk users,
>
> Due to the planned deprecation of gtksourceview2 in Debian,
> we have been working on a stripped down port of LablGtk2 to Gtk-3.
>
> A first beta is available for download at the usual location:
> http://lablgtk.forge.ocamlcore.org
>
> https://forge.ocamlcore.org/frs/download.php/1769/lablgtk-3.0.beta1.tar.gz
>
> There is no opam package yet, because I’m not sure how to do that:
> I seem to need to add a new conf-gtksourceview3 package too, and I’m not
> sure how to proceed. Help accepted.
>
> Note that this is not the originally planned introspection based port, but
> a manual port of lablgtk2, dropping widgets that are no longer
> available. It is of course possible to add new widgets if people
> are willing to contribute.
>
> The main goal is to allow application using lablgtksourceview,
> such as CoqIDE, to compile on top of Gtk-3. Since Gtk-2 itself
> stays available, lablgtk2 will continue to be supported for other
> applications.
>
> The code is in the lablgtk3 branch:
> https://github.com/garrigue/lablgtk/tree/lablgtk3
> There is an ongoing discussion
> https://github.com/garrigue/lablgtk/issues/2
>
> The current status is that a modified version of CoqIDE compiles
> and runs.
>
> Please report issues on GitHub.
>
> Jacques Garrigue
>
> --
> 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
[-- Attachment #2: Type: text/html, Size: 5040 bytes --]
next prev parent reply other threads:[~2018-12-06 10:26 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 [this message]
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
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='CAPFanBGcnTaHAaenFGjyD2Kq_XN7fg-VK=j-WAn7hESjfVJGKw@mail.gmail.com' \
--to=gabriel.scherer@inria.fr \
--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