From: zimoun <zimon.toutoune@gmail.com>
To: 37790@debbugs.gnu.org,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 37790-close@debbugs.gnu.org
Subject: bug#37790: MANPATH missing from non-default profile
Date: Thu, 3 Mar 2022 09:32:50 +0100 [thread overview]
Message-ID: <CAJ3okZ3Z0YgLfX6mDKkc+-VzYFqmTaBfKVwGRMLXEAfOffVqCw@mail.gmail.com> (raw)
In-Reply-To: <87y21rimdg.fsf@gmail.com>
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. :-)
> >> I agree it’s inconvenient, but how would you add an exception?
> >
> > I'm not too sure how Guix works here, but what about when building the
> > profile, systematically populating etc/profile with MANPATH=...?
>
> I don't think special casing ~/.guix-profile like this, polluting other
> profiles is a good idea.
It appears to me the contrary, no? That ~/.guix-profile is special here.
Well, using a multi-profiles style management, it appears to me
adequate to install "man" (or man-db) once, i.e., in one profile say
~/.cache/guix/profiles/utilities, and then install other packages, say
git, in another profile, say ~/, .cache/guix/profiles/tools, etc.
With the current design, each profile other than ~/.guix-profile
requires 'man-db' which seems unfortunate, non?
Cheers,
simon
next prev parent reply other threads:[~2022-03-03 9:09 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 [this message]
2022-03-03 14:04 ` Maxim Cournoyer
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=CAJ3okZ3Z0YgLfX6mDKkc+-VzYFqmTaBfKVwGRMLXEAfOffVqCw@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=37790-close@debbugs.gnu.org \
--cc=37790@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
--cc=maxim.cournoyer@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.