all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: 35864@debbugs.gnu.org
Subject: bug#35864: ~/.local/bin is missing in default PATH on Guix System
Date: Fri, 24 May 2019 12:34:08 +0200	[thread overview]
Message-ID: <20190524103408.rfweixccwqroqgpl@pelzflorian.localdomain> (raw)
In-Reply-To: <87d0k85oud.fsf@roquette.mug.biscuolo.net>

On Fri, May 24, 2019 at 08:49:30AM +0200, Giovanni Biscuolo wrote:
> the "semantic" reason not to include ~/.local/bin in default path is to
> clearly state "use Guix" (even on foreign distros) to allow users to
> install packages and avoid the ~/<something>/bin _broken_ workaround
>
> IMHO at most ~/.local/bin is useful for user written scripts (but I
> prefer ~/bin for mine)
>
> […]
> ...and AFAIU no distribution on earth install packages (or links) in
> ~/.local/bin
> […]
> anyway software projects that want to help users to install (without
> root permissions) in a sane way should define a Guix package, no more
> workarounds please


~/.local/bin is useful for projects at the inception / hacky stage too
or for developers or when they have not been packaged for Guix yet,
but yes, also for user-written scripts.




> Guix deploys in ~/.guix-profile/bin/ linking from the store... and it's
> awesome :-)
> 
> [...]
> 
> > for how-to-install sections in software project README files.
> 
> It's easier to add instructions on how to add ~/.local/bin in $PATH, no?
> :-)
>

Only because not all distros respect ~/.local/bin.  I would prefer
ignoring distros that do not respect ~/.local/bin when writing READMEs
rather than complicating READMEs.



> > I did not know about ~/bin being conventional, but others mention it
> > too.  I do not like ~/bin for the reasons you stated:
> 
> do you mean you don't like it because it's not hidden? :-)
>
> I don't like ~/.local/bin because it's ".local":
> 


Yes; it mixes with the user’s documents.


> «Care should be taken when placing architecture-dependent binaries in
> this place, which might be problematic if the home directory is shared
> between multiple hosts with different architectures.»
> (from [1])
>

This is seldom relevant.


> [...]
> 
> last but not least, probably systemd file-hieracy [1] is one of the
> *problematic* things of systemd ecosystem we should avoid
> 

This is not a fair argument against ~/.local/bin in PATH.

Regards,
Florian

  reply	other threads:[~2019-05-24 10:45 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)
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) [this message]
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=20190524103408.rfweixccwqroqgpl@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=35864@debbugs.gnu.org \
    --cc=g@xelera.eu \
    /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.