On Sat, 14 Dec 2002, Andy Sy wrote: > This is the pain of having dependencies. You might think > that you won't have these problems because you don't > install monolithic packages like X, but you will still > find yourself doing this dependency dance when you try > to install stuff like, say AA support for X, which might > depend on a newer version of Freetype (just a hypothetical > scenario) which might in turn depend on something else... > you get the picture. It's hard enough making sure the > library versions match, but bring in dependency labels into > the mix and the situation quickly becomes hopeless.
Gee a long reply. A few short comments. You are 100% right, for instances wherein you need to 'graft' an alien package into an existing distro, you come up with a whole slew of dependencies. I've encountered that more times than i care to admit, but i don't find it quite a problem, i've recompiled gcc 3.2 and a whole slew of other needed packages on mandrake 7.2, just because i needed to get openoffice compiling and running on that platform. I've invested the time and effort to make these packages THE RPM WAY, simply because when i'm all done, i can simply install the RPMs on any mandrake 7.2 system via a simple command. Sure the tarball way can be done the same way but who wants to keep on repeating those build commands on 30 other boxes? Wheather you do it the RPM way or the tarball way or the slackware pkgtool way you STILL HAVE TO BE AWARE OF DEPENDENCIES. So what's the added value of using lesser technology? _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
