From mboxrd@z Thu Jan 1 00:00:00 1970 From: "pelzflorian (Florian Pelz)" Subject: bug#35864: ~/.local/bin is missing in default PATH on Guix System Date: Fri, 24 May 2019 00:36:14 +0200 Message-ID: <20190523223614.rl2hqtdknhidmccx@pelzflorian.localdomain> References: <20190523122715.2oncjxqvpkl2ylbw@pelzflorian.localdomain> <87ef4pgsql.fsf@elephly.net> <20190523153138.6kspxwfzeisntll5@pelzflorian.localdomain> <87lfyxvuip.fsf@nckx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([209.51.188.92]:58565) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hTwKd-0003dP-OU for bug-guix@gnu.org; Thu, 23 May 2019 18:37:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hTwKc-00007A-Ly for bug-guix@gnu.org; Thu, 23 May 2019 18:37:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:60243) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hTwKc-00006t-97 for bug-guix@gnu.org; Thu, 23 May 2019 18:37:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hTwKc-0000Q0-5A for bug-guix@gnu.org; Thu, 23 May 2019 18:37:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87lfyxvuip.fsf@nckx> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Tobias Geerinckx-Rice Cc: 35864@debbugs.gnu.org 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 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 . 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 (I did not try to confirm this), but Guix does not (need to?) have a package for pip anyway. Regards, Florian