When I moved from BeOS after they went belly up (F) I took a few concepts with me, not the least of which is ~/config and ~/config/bin the latter of which is added to $path. Highly recommend it as a place to home scripts and small compiled programs that don’t need to be system-wide.
Any reason why yould have it in .bash_local over .bashrc? I use zsh but even when I used bash or fish, I’d add to my $PATH via .bashrc and config.fish respectively.
Just to simplify things when I use lots of Linux distros that create different default .bashrc files. Makes it easier to distribute via ansible this way. No other reason really.
When I moved from BeOS after they went belly up (F) I took a few concepts with me, not the least of which is ~/config and ~/config/bin the latter of which is added to $path. Highly recommend it as a place to home scripts and small compiled programs that don’t need to be system-wide.
Isn’t ~/.local for such manually installed stuff, like /usr/local instead of /usr?
.local is a pretty recent convention for somebody who has used BeOS.
I long ago just created $HOME/bin and added it to my path. And it works when I compile things with “–prefix=$HOME”.
OpenSUSE automatically adds ~/bin and ~/.local/bin to your $PATH if they exist.
Nice, other distros may do it now too. It’s been a part of my .bash_local for so long I wouldn’t notice…
Any reason why yould have it in .bash_local over .bashrc? I use zsh but even when I used bash or fish, I’d add to my $PATH via .bashrc and config.fish respectively.
Just to simplify things when I use lots of Linux distros that create different default .bashrc files. Makes it easier to distribute via ansible this way. No other reason really.
BeOS ❤️
Haiku
Wish I could get it to boot on hardware.
~/.local/bin