> Yes, it's entirely possible to do the same thing by > computing package > dependencies, and then interlocking the package > upgrade mechanism so > that you always step from one set to another. The > potential problem > that presents (and the reason why patches are valued > by commercial > customers) is that you often end up forcing users to > take features > they don't want in order to get patches that they > need.
If it was a new behaviour by the updates, I would understand but new features? Tracking patches appears to be a pain. All numbers...just like the docs...makes it very inconvenient to know what is in there. This system is fine for Sun customers. I, however, don't think that third party developers/packagers would like this kind of system. Releasing an updated package and letting the packaging system handle the rest is far less work both ways imho. Send instant messages to your online friends http://uk.messenger.yahoo.com
