From: Maxime Devos <maximedevos@telenet.be>
To: Ekaitz Zarraga <ekaitz@elenq.tech>,
57932@debbugs.gnu.org, control@debbugs.gnu.org
Subject: bug#57932: Mes has overly-generic MES_PREFIX search path (was: `environment_variables` in build containers are set wrong)
Date: Mon, 19 Sep 2022 15:18:21 +0200 [thread overview]
Message-ID: <7a4e8523-e9b1-ed51-16e8-0d1e918693ba@telenet.be> (raw)
In-Reply-To: <86tbaSt8BFnSXLVj8M5X8cW8VmbmVPKmyHMfQQcTEQos0LquGNjLkWrOq4L8zWXMPiHosf_dFpwxKcTv3xAfGHzxLgzEKbNuRt-vcZolsJY=@elenq.tech>
[-- Attachment #1.1.1: Type: text/plain, Size: 1322 bytes --]
retitle 57392 Mes has overly-generic MES_PREFIX search path
thanks
On 19-09-2022 13:17, Ekaitz Zarraga wrote:
> Hi,
>
> I have a package that depends on `mes`.
>
> When I build it with `guix build $package -K` and I jump to the resulting build directory, the `environment_variables` file looks like this:
>
> ```
> [...]
> export MES_PREFIX="/gnu/store/hy6abswwv4d89zp464fw52z65fkzr7h5-perl-5.34.0/"
> ```
>
> The `MES_PREFIX` is set to Perl's installation directory, which is also the first element in `LIBRARY_PATH`.
>
> If I change the order of the package inputs the order of the `LIBRARY_PATH` changes, which is not important, but the first element of `LIBRARY_PATH` is always the one in the `MES_PREFIX`. This doesn't look like the proper behavior: it should always be /gnu/store/*-mes-*
Looking at the search paths of 'mes', it has
(search-path-specification
(variable "MES_PREFIX")
(separator #f)
(files '("")))))
so it 'accept's _all_ the store items. As such, I've renamed the issue
(if you think the new name is inappropriate, feel free to rename it back.)
How about, instead of having a $MES_PREFIX environment variable and
search path, substitute* uses of MES_PREFIX to #$output in a phase?
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2022-09-19 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 11:17 bug#57932: `environment_variables` in build containers are set wrong Ekaitz Zarraga
2022-09-19 13:18 ` Maxime Devos [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7a4e8523-e9b1-ed51-16e8-0d1e918693ba@telenet.be \
--to=maximedevos@telenet.be \
--cc=57932@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=ekaitz@elenq.tech \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).