From: Vivien Kraus via Guix-patches via <guix-patches@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: rg@raghavgururajan.name, 69677@debbugs.gnu.org
Subject: [bug#69677] [PATCH gnome-team 1/1] gnu: opam: Fix build.
Date: Sat, 09 Mar 2024 22:29:26 +0100 [thread overview]
Message-ID: <a9c5fd023074f597736464ae20c20c704b0fe868.camel@planete-kraus.eu> (raw)
In-Reply-To: <a5577e01bd7e3a31ab185229e6aa34d8eaeb2328.camel@gmail.com>
Le samedi 09 mars 2024 à 21:35 +0100, Liliana Marie Prikler a écrit :
> > The solution seems to be for extlib to ship a minimal version. But
> > maybe this should primarily concern the ocaml team, not gnome-team,
> > as it looks to me like a recipe for breaking at least half of the
> > ocaml ecosystem.
> How much of it is broken with gnome-team already (vs. broken on other
> branches)? It wouldn't be nice of us to say "here, we broke it, you
> fix it please". It also appears as though opam only has two
> dependants
> – are we not tracking this correctly or is a minimal version in use
> anyway?
I meant that the fix should maybe be proposed to the OCaml team, not
the GNOME team. I also over-estimated the number of packages that
depend on ocaml-extlib, so it is probably safe.
I opened #69682 for this.
Best regards,
Vivien
next prev parent reply other threads:[~2024-03-09 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 12:08 [bug#69677] [PATCH gnome-team 0/1] Fix opam on gnome-team Vivien Kraus via Guix-patches via
2024-03-09 9:46 ` [bug#69677] [PATCH gnome-team 1/1] gnu: opam: Fix build Vivien Kraus via Guix-patches via
2024-03-09 18:18 ` Maxim Cournoyer
2024-03-09 18:21 ` Vivien Kraus via Guix-patches via
2024-03-09 19:39 ` Vivien Kraus via Guix-patches via
2024-03-09 20:35 ` Liliana Marie Prikler
2024-03-09 21:29 ` Vivien Kraus via Guix-patches via [this message]
2024-03-09 21:35 ` Julien Lepiller
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=a9c5fd023074f597736464ae20c20c704b0fe868.camel@planete-kraus.eu \
--to=guix-patches@gnu.org \
--cc=69677@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=maxim.cournoyer@gmail.com \
--cc=rg@raghavgururajan.name \
--cc=vivien@planete-kraus.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.