WoofyDugfock


Group: Members
Posts: 146
Joined: Sep. 2004 |
 |
Posted: Mar. 22 2005,08:20 |
 |
I can place the binary for an extension I'm making anywhere provided the directory is in the command path.
Is there a preferred location in terms of conforming with linux standards? Does it matter whether it is put in /usr/local/bin or /usr/bin? I'm wondering what they mean by "local" anyway (as in "locally installed software" - everything that's not a base install?) Looking at the location of binaries from a few dsl's, they seem to be all over the place.
(I take it you wouldn't usually put it in /bin).
-------------- "We don't need no stinkin' Windows"
http://news.zdnet.co.uk/software/linuxunix/0,39020390,39149796,00.htm
|