mikshaw


Group: Members
Posts: 4856
Joined: July 2004 |
 |
Posted: Dec. 04 2007,19:35 |
 |
Yes, they usually do, but they are not *intended* for HD installs and therefore are not designed to cope with things such as upgrading existing applications. As this thread demonstrates, if you already have an application installed in /usr, that particular application cannot be upgraded with a uci or tar.gz mydsl package. Even a dsl package might not work, depending on how it was built. If the original application was in /usr/local and the dsl package installs into /usr, the original program will still be the default. Unless the user understands, at least to a point, how the linux filesystem works and how/where the mydsl package installs, that user will continue to run into issues like this. On the other hand, if a user of a traditional HD install goes with Debian packages (apt, synaptic, dpkg) all applications will install into /usr and these opt-isn't-in-path issues will not exist.
-------------- http://www.tldp.org/LDP/intro-linux/html/index.html
|