From: beginner3456789 <beginner3456789@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: PATH duplications
Date: Tue, 25 Feb 2020 23:48:31 +0100 [thread overview]
Message-ID: <20200225224831.0jLFL9kIp8DITFpzOZynyWIVKna3K-Aw3mp4yZ79wzE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18777@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
New comment by beginner3456789 on void-packages repository
https://github.com/void-linux/void-packages/issues/18777#issuecomment-591113548
Comment:
The most recent /etc/profile from base-files 0.140_12 has the PATH appended for everybody just in case somebody wants to create a non-Void chroot. Maybe those creating the chroot could set their own PATH as needed instead of imposing a very wide search for everybody else. Maybe the current PATH settings are just useful during installation for new users?
The final result seems to be very minimal when running bash or dash scripts. Maybe those shells keep a list in memory instead of looking in the file system every time? I set my own PATH for root and user so the default /etc/profile is sort of cosmetic apparently.
@loreb Thanks for the added info. I should close this issue in about a day or so in case anybody else wants to comment.
next prev parent reply other threads:[~2020-02-25 22:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 17:32 [ISSUE] " voidlinux-github
2020-02-13 17:47 ` voidlinux-github
2020-02-14 1:53 ` voidlinux-github
2020-02-15 17:53 ` beginner3456789
2020-02-25 20:58 ` loreb
2020-02-25 20:59 ` loreb
2020-02-25 22:48 ` beginner3456789 [this message]
2020-02-26 23:16 ` [ISSUE] [CLOSED] " beginner3456789
2020-02-27 2:50 ` eli-schwartz
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=20200225224831.0jLFL9kIp8DITFpzOZynyWIVKna3K-Aw3mp4yZ79wzE@z \
--to=beginner3456789@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).