Simon A. Erat wrote:
First of all, whats the acronym FHS standing for?
The Filesystem Hierarchy Standard:
It's linked from the Packaging Guidelines, which I hope you read before you
made your package:
1) At first it was designed to be distributed as tarball, i want to
this option, as this allows an easy port/install to any other linux distro.
(just extract anywhere of your choice and run from there)
It's easier to do that if you give your relocatable directory tree an FHS-like
structure, with a prefix that can be set to "/usr", "/usr/local",
"/opt/Simon's-script-tools" or anything else, and place scripts in
read-only data in $prefix/share et cetera.
You may still find that you need to make your scripts capable of adapting a bit
to different directory layouts.
i currently save any data in $HOME/bin/$USER-libs, and offering
$HOME/bin/$USER-scripts to be used for custom scripts using the functions
which Script-Tools provides.
You shouldn't make subdirectories under $HOME/bin any more than under
/usr/bin. Although users' home directories are less standardized than system
directories, $HOME/bin is typically used for the users' own programs that they
want to be able to run from a command prompt. Programs in subdirectories
wouldn't be found unless the users added the subdirectories to PATH.
Also, anything that ends with "libs" seems like a bad name for a directory to
save data in.