|
From: Thomas L. <ta...@ec...> - 2001-04-24 10:07:22
|
On Mon, Apr 23, 2001 at 08:09:32PM +0200, Jan Wagemakers wrote: > On Mon, 23 Apr 2001, Thomas Leonard wrote: > > > All good points - I've added an 'Application Directories' page to the > > web-site with them on it: > > http://rox.sourceforge.net/appdirs.php3 > Well, I mis something in your text about Application Directories. What about > programs that depends on libraries? How do you install them by making use of > Application Directories? The library could be supplied in a directory of its own (which you drag to /usr/lib to install). There are probably various issues to work out with that, though. For now, I plan to concentrate on the simpler problem of making applications easy to install (although apps often depend on libraries, the library is not usually part of the application). > The reason why I ask this is because I really like the Debian Packaging > system. When I want to install a program I just type > > apt-get install program > > when this program depends on other files (libraries) these files will > also get installed. When I want to remove the program I just type : > > apt-get remove program > > Simple! Yep, Debian handles all the dependancies for you. Hopefully, many of the ROX apps will end up in the Debian system. However, apt-get install is no use if you don't have root access! Hmm... I wonder how much faster dpkg would be if everything was self-contained... that's got to make checking for conflicts easier! > But when we make use of appdirs, how do we automate the installation of other > necessary files? Is the concept of seperating libraries and program-files > still useable with Application Directories? Libraries certainly should be separate. I'd keep the current system for now, and just accept that installing libraries will be harder than installing applications :-/ -- Thomas Leonard http://rox.sourceforge.net ta...@ec... ta...@us... |