From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 35864@debbugs.gnu.org
Subject: bug#35864: ~/.local/bin is missing in default PATH on Guix System
Date: Fri, 24 May 2019 00:36:14 +0200 [thread overview]
Message-ID: <20190523223614.rl2hqtdknhidmccx@pelzflorian.localdomain> (raw)
In-Reply-To: <87lfyxvuip.fsf@nckx>
On Thu, May 23, 2019 at 09:31:09PM +0200, Tobias Geerinckx-Rice wrote:
> pelzflorian (Florian Pelz) wrote:
> > Adding ~/.local/bin to the PATH is common on other distros.
>
> This is what still needs to be established: is it? Which ones? Is it merely
> a side-effect of them using systemd? And most crucially: does it mean that
> Guix needs to add it too? What about ~/bin?
>
My motivation was that I would have liked a uniform standard to exist
for offering uniform, simple compilation instructions in tutorials
like mine
<https://pelzflorian.de/gui-prog-gtk-2017/handout-05-meson-en.pdf> or
for how-to-install sections in software project README files. I
therefore believe such standardization efforts should be supported,
even though Guix has good reason to ignore some other aspects of the
file-system hierarchy standard.
I checked now and systemd Parabola iso images and installed systems do
not include ~/.local/bin; neither does an installed Arch system I
looked at, despite their claim to follow
<https://wiki.archlinux.org/index.php/Frequently_asked_questions#Does_Arch_follow_the_Linux_Foundation's_Filesystem_Hierarchy_Standard_(FHS)?>.
I believe this may have to do with their tendency to ship programs
mostly like their upstream developers ship them, which would apply to
GNU Guix as well. Many other distributions are discussed at my
stackexchange link from before.
I did not know about ~/bin being conventional, but others mention it
too. I do not like ~/bin for the reasons you stated:
On Thu, May 23, 2019 at 04:55:28PM +0200, Tobias Geerinckx-Rice wrote:
> My theory is that it's intended for users of graphical file browsers (where
> the traditional ~/bin is a bit too prominent even for my tastes), but I use
> it too.
>
> I'm was just interested in the (ideally: your) arguments for doing so, not a
> link to a discussion site. If it really breaks things that should work, I'm
> all in favour of adding it to the default skeleton, if not /etc/profile
> itself.
>
I am not aware of it fixing any breakage, except Python pip according
to the Debian bug report
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856> (I did not
try to confirm this), but Guix does not (need to?) have a package for
pip anyway.
Regards,
Florian
next prev parent reply other threads:[~2019-05-23 22:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 12:27 bug#35864: ~/.local/bin is missing in default PATH on Guix System pelzflorian (Florian Pelz)
2019-05-23 14:17 ` Ricardo Wurmus
2019-05-23 15:31 ` pelzflorian (Florian Pelz)
2019-05-23 19:31 ` Tobias Geerinckx-Rice
2019-05-23 22:36 ` pelzflorian (Florian Pelz) [this message]
2019-05-24 5:23 ` pelzflorian (Florian Pelz)
2019-05-24 6:17 ` Ricardo Wurmus
2019-05-24 10:36 ` pelzflorian (Florian Pelz)
2019-05-24 6:49 ` Giovanni Biscuolo
2019-05-24 10:34 ` pelzflorian (Florian Pelz)
2019-05-23 14:55 ` Tobias Geerinckx-Rice
2019-05-23 15:54 ` pelzflorian (Florian Pelz)
2019-05-23 19:35 ` Tobias Geerinckx-Rice
2019-05-23 19:55 ` Jesse Gibbons
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=20190523223614.rl2hqtdknhidmccx@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=35864@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.