GNU bug report logs - #57932
Mes has a catch-all search path

Previous Next

Package: guix;

Reported by: Ekaitz Zarraga <ekaitz <at> elenq.tech>

Date: Mon, 19 Sep 2022 11:18:02 UTC

Severity: normal

To reply to this bug, email your comments to 57932 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#57932; Package guix. (Mon, 19 Sep 2022 11:18:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Ekaitz Zarraga <ekaitz <at> elenq.tech>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Mon, 19 Sep 2022 11:18:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ekaitz Zarraga <ekaitz <at> elenq.tech>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Subject: `environment_variables` in build containers are set wrong
Date: Mon, 19 Sep 2022 11:17:15 +0000
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 LIBRARY_PATH="/gnu/store/hy6abswwv4d89zp464fw52z65fkzr7h5-perl-5.34.0/lib:/gnu/store/22n2s0vfvqg9v0as9h7fpdn1i9dmryvi-texinfo-6.7/lib:/gnu/store/kijj8bhcaz984jbgbshrdabzd07cg1zv-mes-0.24/lib:/gnu/store/s3hl12jxz9ybs7nsy7kq7ybzz7qnzmsg-bzip2-1.0.8/lib:/gnu/store/c8isj4jq6knv0icfgr43di6q3nvdzkx7-xz-5.2.5/lib:/gnu/store/4ic6244i3ca4b4rxc2wnrgllsidyishv-file-5.39/lib:/gnu/store/690qz3fg334dpwn3pn6k59n4wc943p2b-gawk-5.1.0/lib:/gnu/store/rc781v4k0drhaqn90xfwwpspki5x0bvf-binutils-2.37/lib:/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib:/gnu/store/4jdghmc65q7i7ib89zmvq66l0ghf7jc4-glibc-2.33-static/lib:/gnu/store/fnr1z6xsan0437r0yg48d0y8k32kqxby-glibc-utf8-locales-2.33/lib:/gnu/store/9xn2y515vv9p0vgww4add3lphwi17q07-nyacc-1.00.2/lib"
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-*

Best,
Ekaitz




Information forwarded to bug-guix <at> gnu.org:
bug#57932; Package guix. (Mon, 19 Sep 2022 13:19:02 GMT) Full text and rfc822 format available.

Message #8 received at 57932 <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: Ekaitz Zarraga <ekaitz <at> elenq.tech>, 57932 <at> debbugs.gnu.org,
 control <at> debbugs.gnu.org
Subject: Re: 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
[Message part 1 (text/plain, inline)]
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.
[OpenPGP_0x49E3EE22191725EE.asc (application/pgp-keys, attachment)]
[OpenPGP_signature (application/pgp-signature, attachment)]

Changed bug title to 'Mes has a catch-all search path' from '`environment_variables` in build containers are set wrong' Request was from Ludovic Courtès <ludo <at> gnu.org> to control <at> debbugs.gnu.org. (Fri, 23 Sep 2022 06:23:02 GMT) Full text and rfc822 format available.

This bug report was last modified 2 years and 264 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.