You are not logged in.
I've created a PKGBUILD for this tool, that's a bash script expected to be source'd in your .bashrc. Now, in the PKGBUILD I've pushed to the AUR I install that script to /etc/bash-preexec/bash-preexec.sh though I'm afraid that's non-standard. I wanted to hear where it's advised to put those kind of scripts and what would you have done.
Last edited by giuscri (2017-06-06 18:19:00)
Offline
/usr/bin
As all executables...
Offline
No, not /usr/bin as these are not meant to be executed - they are meant to be sourced. I think /etc/profile.d/ could be an option. (edit: maybe not).
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
I guess it's a holy war between /etc and /usr/share. The longer I think about it I'm more inclined to /usr/share as those are usually read only files, as is the script. /etc contains dynamic configuration files. Though I wouldn't be surprised by either choice.
Offline
No, not /usr/bin as these are not meant to be executed - they are meant to be sourced.
I think /etc/profile.d/ could be an option.(edit: maybe not).
If the file is meant to be sourced by all users on the system then /etc/profile.d may well be the right place, but I would not want to use that system
/usr/share/<app>/wherever is probably the best place (that's where makepkg keeps its Bash sourceables). /etc/ is mostly for config files.
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
I would concur with the /usr/share/<app> suggestion.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline