[clug] path with wildcards

[Kim Holburn]

What's wrong with /usr/bin or /bin?

And add completion to /etc/bash_completion.d
add man pages to /usr/share/man/man.?

Only things you make yourself should be in /usr/local/bin.

Isn't there a standard for this like LSB or Linux file hierarchy?

On 2007/Aug/02, at 8:52 AM, Michael.James at csiro.au wrote:

> Where should a package put its executables?
>
> If it's big then   /opt/<big-package>/bin/
>   and add that dir to the path with   /etc/profile.d/<big-package>.sh
>
> If it's tiny          /usr/local/bin/
>
> If it's middling then maybe  /opt/(small-package>/bin/
>   with a full set of soft links in  /usr/local/bin
>
> But the upshot is a lot of  /usr/local/bin/
>   dirs with generations of un-traceable cruft.
>
> Is there any way to have sub-dirs included in the path?
>
> export PATH='~/.bin:opt/bin/*:/usr/bin:/bin'
>
> ls -l /opt/bin/*
>
> /opt/bin/big-package -> /opt/big-package/bin
> /opt/bin/bin  ->  /usr/local/bin
> /opt/bin/tiny-package/my1st-executable
> /opt/bin/tiny-package/my2nd-executable
> /opt/bin/tiny-package/my3rd-executable
>
>
> It would help us on the way to the plug-in style of
> Initialization script in	/etc/profile.d
> Libraries in	/etc/ld.so.conf.d/
>
> michaelj
>
> -- 
> Michael James                         michael.james at csiro.au
> System Administrator                    voice:  02 6246 5040
> CSIRO Bioinformatics Facility             fax:  02 6246 5166
>
> No matter how much you pay for software,
>  you always get less than you hoped.
> Unless you pay nothing, then you get more.
> -- 
> linux mailing list
> linux at lists.samba.org
> https://lists.samba.org/mailman/listinfo/linux

--
Kim Holburn
IT Network & Security Consultant
Ph: +39 06 855 4294  M: +39 3494957443
mailto:kim at holburn.net  aim://kimholburn
skype://kholburn - PGP Public Key on request

Democracy imposed from without is the severest form of tyranny.
                           -- Lloyd Biggle, Jr. Analog, Apr 1961