On Mon, 22 Apr 2002, Koen van der Drift wrote: > Suppose I have a package (A) installed that depends on another > package (B). Now package B is updated - should I then rebuild > package A too, even though it is not updated?
Generally, no. The reason functionality gets offloaded to shared libraries is Good Software Engineering: changes to the library shouldn't require a matching change to the application that depend on it, & vice versa. You split things up so that you don't *need* to rebuild things all the time. This is not much different from the way you didn't have to upgrade all the software on your computer every time you upgraded from OSX 10.1.0 to 10.1.1, 10.1.2, 10.1.3, 10.1.4... Even though all the software depends on the OS, changes in the OS are supposed to be isolated from software running on top of it. At least, as long as nothing accidentally broke :) -- 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
