mikshaw
Group: Members
Posts: 4856
Joined: July 2004 |
 |
Posted: Aug. 16 2004,20:09 |
 |
That's not a bad idea, but it still doesn't address the possibility of overwriting libs between extensions, because you're still using a shared lib directory. What I hope to achieve is a way to point a specific application to a specific lib directory, i.e. $PREFIX/lib.
Additionally, my hope is to keep from making any chages to the base DSL system...writing to /etc/ld.conf.so is not an option for me.
It seems that one issue I'm trying to avoid stems from the way in which DSL extensions work as opposed to typical packages such as .deb, and to apt-get. Apt-get, for example, checks for dependencies and downloads them if necessary. With DSL extensions, the packager manually deals with dependency checking while putting together the package. After this point, there is no checking...the package is simply installed, and if the user already has a particular file, whether it be the actual lib or a symlink, that file is overwritten automatically. This could cause previously installed programs to fail. I don't know what the chances of this are, but the fact remains that it is a possibility.
It would help if I understood better about modifying sources...i know a decent amount about bash, but next to nothing about programming.
--------------
http://www.tldp.org/LDP/intro-linux/html/index.html
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
