all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>,
	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 08:49:30 +0200	[thread overview]
Message-ID: <87d0k85oud.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <20190523223614.rl2hqtdknhidmccx@pelzflorian.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2521 bytes --]

Hi Florian,

this is not a bug, it's a feature :-)

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)

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:

> 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.

[...]

> My motivation was that I would have liked a uniform standard to exist
> for offering uniform, simple compilation instructions

I can't understand what ~/.local/bin have to do with *compilation*: do
you mean installation?

...and AFAIU no distribution on earth install packages (or links) in
~/.local/bin

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?
:-)

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

[...]

> Many other distributions are discussed at my stackexchange link from
> before.

not Guix nor Nix, IMHO it's because they choose to depart from the
problematic FSH and derivatives long time ago and for this reason they
are generally ignored when discussing FSH issues

> 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":

«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])

[...]

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

...I even ignored the existance of systemd file-hieracy: an init system
defining a filesystem hieracy standard: mumble...




Happy hacking! Gio'.



[1] https://www.freedesktop.org/software/systemd/man/file-hierarchy.html

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2019-05-24  6:51 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 [this message]
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=87d0k85oud.fsf@roquette.mug.biscuolo.net \
    --to=g@xelera.eu \
    --cc=35864@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=pelzflorian@pelzflorian.de \
    /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.