$ head -n 3 /usr/bin/push.sh #! /bin/sh # (C) Martin V\"ath <vaeth@mathematik.uni-wuerzburg.de> # This script is meant to be sourced; the first line is only for editors Then why install it in /usr/bin/ instead of say, /usr/share/push/ ? And category is propably wrong too, dev-libs/ would have propably suited more better, but that's just cosmetics so whatever If you strongly disagree, feel free to close as WONTFIX, won't pursue this futher
The natural location to install a "global" shell-script is in the PATH: From "man 1p dot": [...] the shell shall use the search path specified by PATH to find the directory containing file. Unlike normal command search, however, the file searched for by the dot utility need not be executable. [...] So only after installation into PATH the natural command . push.sh will work (which can then be expected to work also on non-gentoo systems [e.g. on prefix] without any special treatment). There is no reason to make loading more complicated than necessary. Concerning the category: dev-libs seems to contain only binary libraries while dev-shell contains shell-helper things like "localshell", "bashish", or "bash-completion". I am not strictly against a package move to dev-libs, but I see then also a danger of name collission: Although, currently, I am not aware of another project called "push", there might be some in the future (since this name is so simple), and if there ever should be a library with that name, there is serious trouble just because of a name collission with such a small "script project": Note that there is no way to "undo" a move command. Summarizing, I suggest to keep both as it is now.
OK, then. Like I said, I have no strong preference.
This is older than bug 598527, but current discussion is in the newer bug. Therefore, duping it "the wrong way around". *** This bug has been marked as a duplicate of bug 598527 ***
