From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: 20255@debbugs.gnu.org
Subject: bug#20255: 'search-paths' should respect both user and system profile.
Date: Mon, 23 Nov 2015 00:04:09 +0100 [thread overview]
Message-ID: <87h9kdy6ty.fsf@gnu.org> (raw)
In-Reply-To: <877fl9q3gv.fsf@gmail.com> (Alex Kost's message of "Sun, 22 Nov 2015 21:44:00 +0300")
Alex Kost <alezost@gmail.com> skribis:
> Ludovic Courtès (2015-11-22 13:52 +0300) wrote:
[...]
>> To me, what 宋文武 reported at the beginning of this thread is a
>> usability issue. We’ve hacked around it so far, but we know there are
>> cases where the hacks aren’t enough.
>>
>> We could declare it as “won’t fix”, but I’m not comfortable with that.
>
> No, no, I'm against “won't fix”. I don't mind if it's called a bug, and
> a solution you suggest is the best,
OK.
> but it suits only the default case of a single user profile. If I
> have several user profiles, it does nothing useful for me, only wastes
> the time.
I think this is fine. ~/.guix-profile is treated specially in many
ways. I think users do not expect other profiles to be magically taken
into account.
> OK, for the bug at hand, invoking "guix package --search-paths" looks
> like the only possible solution, but please don't commit this patch
> without giving a user a chance to decide what to put in /etc/profile.
OK.
>> The solution I came up with might be inadequate. Then we need to come
>> up with an alternate proposal, or to resign and mark it as “wontfix.”
>
> It is adequate and I'm not against it.
OK. To me, that it takes 2 seconds on your machines suggests that it’s
not great either.
>> What would you suggest?
>
> After all, I realized what is my main concern: "/etc/profile" is
> non-editable. If I don't like some pieces of this file, I can do
> nothing, and I just have to live with it and suffer. Ideally I would
> like to decide what pieces I want to put in /etc/profile and what I
> don't. But it's probably not possible, so…
>
> … what I suggest now is just to give an option to avoid generating the
> default /etc/profile. What about making an 'operating-system' field for
> this file (similar to 'sudoers-file' or 'hosts-file')? So when such
> 'profile-file' is specified, it will be used instead of the default one
> (of course, it should be mentioned in the manual that it's only for
> those users who are sure what they do).
I think we could make an /etc/profile-service that receives snippets
meant to be glued together into the final /etc/profile. Users could
specify the top or bottom of the file.
There could be a combined-search-paths-service that implements the
solution I proposed here.
WDYT?
> If this 'profile-file' field appears, I will gladly use it, and I will
> not object to any future changes in /etc/profile.
Of course we want to offer this flexibility. But I think it’s also
important to discuss the defaults, to make sure they are acceptable to
many and that they improve the “user experience.”
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-11-22 23:05 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-04 10:29 bug#20255: 'search-paths' should respect both user and system profile 宋文武
2015-04-04 21:04 ` Ludovic Courtès
2015-04-05 3:39 ` 宋文武
2015-04-05 18:15 ` Ludovic Courtès
2015-04-06 4:02 ` 宋文武
2015-04-06 8:24 ` Mark H Weaver
2015-05-02 22:12 ` Ludovic Courtès
2015-11-19 22:32 ` Ludovic Courtès
2015-11-20 22:42 ` Alex Kost
2015-11-21 8:57 ` Ludovic Courtès
2015-11-21 18:41 ` Alex Kost
2015-11-21 20:10 ` Ludovic Courtès
2015-11-22 7:52 ` Alex Kost
2015-11-22 10:52 ` Ludovic Courtès
2015-11-22 18:44 ` Alex Kost
2015-11-22 23:04 ` Ludovic Courtès [this message]
2015-11-23 11:55 ` Alex Kost
2015-11-23 14:31 ` Ludovic Courtès
2015-11-24 17:22 ` Ludovic Courtès
2015-11-30 9:08 ` Alex Kost
2015-11-30 12:25 ` Ludovic Courtès
2015-05-04 21:44 ` Ludovic Courtès
2015-05-05 8:28 ` 宋文武
2015-05-05 12:35 ` Ludovic Courtès
2015-05-06 16:35 ` Ludovic Courtès
2015-11-12 11:13 ` Ludovic Courtès
2020-02-21 15:53 ` bug#20255: (old)bug#20255: 'search-paths' should respect both user and system profiles zimoun
2020-02-21 17:18 ` Alex Kost
2021-06-26 2:37 ` bug#20255: 'search-paths' should respect both user and system profile Maxim Cournoyer
2021-06-26 5:59 ` Leo Prikler
2021-06-28 4:35 ` Maxim Cournoyer
2021-06-28 6:58 ` Leo Prikler
2021-06-27 9:59 ` Alex Kost
2021-06-28 4:48 ` Maxim Cournoyer
2021-06-29 17:29 ` Alex Kost
2020-12-18 20:27 ` bug#20255: «the Oldest» [PATCH] 'search-paths' should respect both user and system profiles zimoun
2023-05-12 12:34 ` bug#20255: 'search-paths' should respect both user and system profile 宋文武 via Bug reports for GNU Guix
2023-05-15 13:53 ` Maxim Cournoyer
2023-05-15 17:14 ` Josselin Poiret via Bug reports for GNU Guix
2023-05-15 17:46 ` Maxim Cournoyer
2023-05-16 9:37 ` Josselin Poiret via Bug reports for GNU Guix
2023-05-16 11:00 ` 宋文武 via Bug reports for GNU Guix
2023-05-17 14:04 ` bug#20255: [PATCH 1/4] home: shells: Merge search-paths of multiple profiles iyzsong--- via Bug reports for GNU Guix
2023-05-17 14:04 ` bug#20255: [PATCH 2/4] system: default-skeletons: Set up Guix home profile when it exists iyzsong--- via Bug reports for GNU Guix
2023-05-17 14:04 ` bug#20255: [PATCH 3/4] system: Only source system profile's settings in '/etc/profile' iyzsong--- via Bug reports for GNU Guix
2023-05-17 14:04 ` bug#20255: [PATCH 4/4] news: Add entry for '/etc/profile' changes iyzsong--- via Bug reports for GNU Guix
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=87h9kdy6ty.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=20255@debbugs.gnu.org \
--cc=alezost@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 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).