On Wednesday 03 January 2007 23:09, Dominique Leuenberger wrote: > >>> Reply on 04-01-2007 9:05:08 <<< > > > > IMO, don't use dependencies. > > > > If you're program/application requires a dependency, then provide it in > > the > > package. You can easily write an installation routine to check if the > > required libraries are present and then install them in a sub-folder of > > your > > application if they're not. > > > > > > I'm still not quite sure where SUSE stores programs - it seems some are > > > > in /etc/bin, others in /usr/bin and still others in /opt/kde3/bin. > > Ok, as it's an opinion I will not say it's wrong :-) but I can't really > agree on this. Why should every single thing bring all the libs it leends > and bloat the system like this? YOU might not care about disk space, about > downloadsize... but believe me: you're not alone out there. >
It shouldn't necessairly. As I mentioned in my post, the package installer can check if the lbrary is installed. If it is a supported library, then maybe the installer can download from the repository. If not, then include it. Dunno. > Having the dependencies is a powerful method to keep packages small, and > MANY libraries ARE used more than once. No argument there. I'm just thinking of specialized ones which may not be included with the distribution and should then - maybe - become the responsibility of the programmer/project manager. -- kai - [EMAIL PROTECTED] www.perfectreign.com || www.4thedadz.com www.filesite.org || www.donutmonster.com wo ist der ort für den ehrlichsten kuss ich weiss, dass ich ihn für uns finden muss... -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
