From: Julien Lepiller <julien@lepiller.eu>
To: 69677@debbugs.gnu.org, liliana.prikler@gmail.com,
vivien@planete-kraus.eu, maxim.cournoyer@gmail.com
Cc: rg@raghavgururajan.name
Subject: [bug#69677] [PATCH gnome-team 1/1] gnu: opam: Fix build.
Date: Sat, 09 Mar 2024 22:35:12 +0100 [thread overview]
Message-ID: <A2836F66-8014-4CAA-9585-520FAB5899B2@lepiller.eu> (raw)
In-Reply-To: <a5577e01bd7e3a31ab185229e6aa34d8eaeb2328.camel@gmail.com>
Le 9 mars 2024 21:35:43 GMT+01:00, Liliana Marie Prikler <liliana.prikler@gmail.com> a écrit :
>Hi Vivien,
>
>Am Samstag, dem 09.03.2024 um 20:39 +0100 schrieb Vivien Kraus:
>> My guess is that we have 2 ocaml libraries implementing Base64
>> (ocaml-base64 and ocaml-extlib, propagated from ocaml-dose3). Dune
>> sees that we have a powerful ocaml-base64 installed, so it lays out
>> the compatibility version 6 for us, but when it comes to actually
>> building the project, ocamlfind prioritizes the ocaml-extlib path by
>> adding it first, and it shadows our powerful ocaml-base64
>> implementation.
>>
>> With this new extlib actor in the plot, I could search better. It
>> seems like Opam is aware of the issue:
>>
>> https://github.com/ocaml/opam/issues/5694
>>
>> 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.
Sounds like we could switch extlib to the dune build-system, possibly adding a #:package argument to make sure it doesn't build the compat version.
>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?
opam is not used to build ocaml packages, so it's not a surprise to me it has so few dependents. Would be nice not to break it though, it's still a useful program by itself :)
>
>Cheers
>
>
>
prev parent reply other threads:[~2024-03-09 21:36 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
2024-03-09 21:35 ` Julien Lepiller [this message]
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=A2836F66-8014-4CAA-9585-520FAB5899B2@lepiller.eu \
--to=julien@lepiller.eu \
--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.