On Tue, Dec 06, 2005 at 03:42:07PM -0500, Jeff Spaleta wrote: > > If it's known that package is going to be added to extras at some point > > soon, that package probably shouldn't be added to the obsoleted-packages > > list. > As soon as we get that read-the-future plugin into the Extras > buildsystem. As an exercise for the reader... how many dropped Either that or the "better coordination between core and extras" plugin. > packages in FC4 that were in FC3 were submitted for review before FC4 > release? How many were submitted after FC4 release? Early-growth time for extras; not really a benchmark for normal future operation -- or at least, I hope not. > > I'm more concerned about the ones that do have broken deps, which seems to > > be a lot of the time in cases like this. > If installed packages have broken deps.... hasn't anaconda in the past > advised you of this as part of the install? fc5t1 anaconda doesn't If I remember right, the pre-anaconda installer did, and would make you pick "proceed anyway". Anaconda, however, just spits out some warnings to one of the text consoles and goes on its merry way. FC5t1 doesn't count since it doesn't do upgrades at all. :) > count since its clearly not representative of full anaconda > functionality. I don't see why this is a concern unless anaconda is > going to start handling upgrade situation differently. Well, it's a concern because currently, upgraded systems accumulate cruft.a > > It still could be; the obsoletes-packages RPM would just be a tool to > > help if you decide to go that way. > If you install obsoletes-packages... there is no decision point. If > obsoleteing is active in the transaction, it obsoletes all the > packages that is set to obsolete.. like all other obsoletes in all > other packages. For this package to be a tool to help you "decide", it > would have to be treated differently than all other obsoletes in all > other packages which obsolete without user interaction. Are you know > suggesting that this mythical obsoletes-package be treated specially > by the tools? Anaconda certainly treats a lot of packages specially. And if an admin wants to prevent this from happening, he or she could add it to the list of packages yum ignores. -- Matthew Miller mattdm@xxxxxxxxxx <http://mattdm.org/> Boston University Linux ------> <http://linux.bu.edu/> -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
