mikshaw


Group: Members
Posts: 4856
Joined: July 2004 |
 |
Posted: Sep. 28 2005,15:57 |
 |
You should NOT have a /usr/bin/myapp in a .tar.gz or .uci package. There should be nothing that writes to /usr, /bin, /boot, /lib, or /sbin. These directories are all initially read-only. After mkwriteable has run (e.g. after loading a .dsl package) you can load files into these directories from a .tar.gz package, but by that time there's not much point in it being a tar.gz. For the sake of consistency, it's best to use a .dsl package for anything that needs to go into these directories.
I don't see why it's such a trouble to add bin directories to your PATH variable manually...it's one of the basic parts of being a linux user. If you are really that concerned with ease-of-use, just make your application a .dsl package that installs into /usr. If you go through the trouble of making an html page you could have set the PATH a hundred times over in that time.
I have no idea what your last sentence is saying. The PATH is explored every time you issue a command (gadzillions of times a day). There is no uncompressing required when this happens.
-------------- http://www.tldp.org/LDP/intro-linux/html/index.html
|