all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Pierre Neidhardt <mail@ambrevar.xyz>,
	37790-close@debbugs.gnu.org, 37790@debbugs.gnu.org
Subject: bug#37790: MANPATH missing from non-default profile
Date: Thu, 03 Mar 2022 09:04:56 -0500	[thread overview]
Message-ID: <87lexri12v.fsf@gmail.com> (raw)
In-Reply-To: <CAJ3okZ3Z0YgLfX6mDKkc+-VzYFqmTaBfKVwGRMLXEAfOffVqCw@mail.gmail.com> (zimoun's message of "Thu, 3 Mar 2022 09:32:50 +0100")

Hi Simon,

zimoun <zimon.toutoune@gmail.com> writes:

> Hi Maxim,
>
> On Thu, 3 Mar 2022 at 07:26, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>
>> tags 37790 notabug
>
> From my understanding, it is a "bug" as explained here:
>
> 1: <https://issues.guix.gnu.org/37790#2>
>
> Or at least an inconvenient behaviour. :-)

Sorry, I fail to see where is the bug :-).  This is our the search-path
specifications have always worked; they work per profile and are
attached to the application acting as the "consumer" of the environment
variable it sets.

If we want to work on improving this we already have the following
issues opened awaiting work:

20255 'search-paths' should respect both user and system profile.

and somewhat related:

22138 Search paths of dependencies are not honored

Thanks,

Maxim




      reply	other threads:[~2022-03-03 14:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17 12:58 bug#37790: MANPATH missing from non-default profile Pierre Neidhardt
2019-10-17 14:54 ` Ludovic Courtès
2019-10-17 15:11   ` Pierre Neidhardt
2019-10-17 16:17     ` Ludovic Courtès
2019-10-18  8:20       ` Pierre Neidhardt
2022-03-03  6:24         ` Maxim Cournoyer
2022-03-03  8:32           ` zimoun
2022-03-03 14:04             ` Maxim Cournoyer [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=87lexri12v.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=37790-close@debbugs.gnu.org \
    --cc=37790@debbugs.gnu.org \
    --cc=mail@ambrevar.xyz \
    --cc=zimon.toutoune@gmail.com \
    /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.