From: Tobias Geerinckx-Rice <me@tobias.gr>
To: 35864@debbugs.gnu.org
Subject: bug#35864: ~/.local/bin is missing in default PATH on Guix System
Date: Thu, 23 May 2019 21:31:09 +0200 [thread overview]
Message-ID: <87lfyxvuip.fsf@nckx> (raw)
In-Reply-To: <20190523153138.6kspxwfzeisntll5@pelzflorian.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
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?
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.
> When compiling and installing software as a user without making
> a package
> for it, I want to configure it with --prefix=$HOME/.local so I
> can
> install without sudo. Then I want to be able to run:
>
> myprog
>
> instead of
>
> PATH=$HOME/.local/bin myprog
You can already easily add custom directories to $PATH in your
.bash_profile, if my understanding of bash's complicated set of
configuration files is still accurate. That's where I set it,
anyway:
~ λ grep PATH= .bash_profile
PATH="$HOME/.local/bin:$PATH"
and it's always worked fine. :-)
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-05-23 19:32 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 [this message]
2019-05-23 22:36 ` pelzflorian (Florian Pelz)
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
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=87lfyxvuip.fsf@nckx \
--to=me@tobias.gr \
--cc=35864@debbugs.gnu.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.
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).