On Sat, 20 Apr 2002, Nicholas Robbins wrote: > Ok, what I still don't understand is: I am not adding anything, just > updating, so why did my already installed packages now need 45 new > things? It looks like 20 of them are splitings of packages I already > have, like esound and gimp, so those I understand. But why do I need 25 > new packages? I just updated. I already had gimp, esound, xemacs, > xfree86 installed, so shouldn't all of their dependencies be installed > as well?
*shrug* It's not uncommon for updates to bring in new dependencies (or, I suppose, to remove old ones, though you wouldn't notice that as much unless you were looking for it). Maybe the new versions bring in new functionality, or rewrite old features in such a way that they uses these other packages to do old functions, or old functions or spun off but still needed, or... there could be lots of reasons I suppose. In the long run, I don't think this is such a big deal, because new packages can be brought in using packages you'll have already (thus they can be smaller & more reliable, because already-working components are in place at the outset). I switched from stable/* to unstable/* a month or two ago, and had to go through the same process -- I think I had to upgrade about the same number of packages (two or three dozen), and had like 50 or 60 new dependencies -- but once it was all installed it has been easy to keep abreast with things (most projects don't update very often) and when installing anything new I usually already have most of what is needed. Think of it as a one time expenditure or something. If you've got the disc space, and can leave the machine compiling for a weekend or so, it's not really a problem after that. *shrug* -- Chris Devers [EMAIL PROTECTED] Apache / mod_perl / http://homepage.mac.com/chdevers/resume/ "More war soon. You know how it is." -- mnftiu.cc _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
