Thank you for your elaborate response!
I brought up the standards to simply understand if there are any benefits following them. After the whole discussion it seems it does not matter at all for my personal needs (but now I have a more informed understanding).
What I really liked is learning about the Fish shells ~/.config/fish/functions directory, this IMHO makes sense in contemporary Linux and is a great idea.
My scripts all have a prefix, so I don’t mind having them in my path, they won’t clash with regular commands. This way, when I run a script which gets executed only annually, I can just type prefix- and TAB and will find it.
Nice! Thanks for chiming in with how Fish does it, sounds like a really great idea to have functions in ~/.config/fish/functions!
Thank you so much, bookmarked all of your links! :-)
Thanks, I think I get the idea, I just don’t understand the number-prefix, why did you start this convention?
(Btw.: For some years now I stick to the convention, that everything import is under one sub directory under my home. As long as I have a tarball backup of that sub directory, I am good to lose the whole hard disk w/o fear (e.g. ready for a clean upgrade, distro hop or just go traveling w/o fearing that I forgot to switch off the oven ;-)).
Another follow up question: Is there any documentation for the linux standard/convention of ~/.local/bin? My initial search about this resulted in nothing which I would call authoritative/definitive.
Thank you very much! I was exactly looking for someone telling me that some tools install their own binaries/scripts to ~/.local/bin.
Most probably I’ll just symlink my scripts from ~/.local/bin then, this would avoid troubles with 3rd partys and most of my dotfiles are symlinked anyway, so the infrastructure is there.
Thanks! Do you just put the whole .local/bin under source control, do you link your scripts from somewhere else?
Debian stable (ok, writing this on Debian Trixie which is not stable yet, but nonetheless works w/o trouble in a virtual machine).
I am using Debian for work and on my servers.
Why Debian? Because for my use cases there are no real alternatives at this moment.
Every 6 month I’ll boot Fedoras live cd and play around with the newest Gnome/KDE, but seriously, for at least the last 5 years I never feel like essential improvements are pushed in the newest iterations of Gnome/KDE and I can happily wait the maximum of 2 years until they are released with Debian.
Saying that, I also own a Steam Deck and as an entertainment/media station I totally love what Valve is doing there. I would also be totally happy to run a De-Googled ChromeOS if it would support all the platforms/software etc. I need. For containers I’ll also happily use Alpine Linux, if it is possible, but again, I’ll mostly default to Debian simply because I know my way around.
In the end, an operating system is just a necessary evil to allow me to do what I want to do with a computer. As long as I have a stable OS which I can tweak to my liking/needs automatically and central package management, I am good. (Unless it is your hobby to play around with your operating system ;-)).
Count me in! The old installer hat a great UX for people knowing what they wanted to do… There must be dozens of us, dozens! ;-)
wow, thanks. I never had the need for scripts running in the right order for my personal scripts, but I remember the old init systems for Linux where this was a thing.