yum annoyances
Matthew Miller
mattdm at mattdm.org
Tue Dec 6 18:52:28 UTC 2005
On Tue, Dec 06, 2005 at 12:22:22PM -0500, Jeff Spaleta wrote:
> > This could be worked around with an "obsolete-packages" rpm in the
> > repository, which would mark as Obsolete all such known packages.
> Is that really appropriate? To unleash a package in a repository that
> will remove functionality from a client system? What happens to user
> who were relying on that functionality?
Well, if they're using Rawhide, they should by definition not be relying on
anything. And in a stable release, this shouldn't happen except between
releases (where it often does).
> Its one thing to obsolete because of a package name change where the
> new package provides similar functionality. Its quite another when
> obsoleting is used in a blank payload package to delibrately remove
> another package without actually providing similar functionality.
Also, the obsoletes tags in such a package would need to precise, so they
match the version-release of the latest Core/Extras package but not beyond
that, so that there wouldn't be a problem with other repos providing the
same package.
--
Matthew Miller mattdm at mattdm.org <http://mattdm.org/>
Boston University Linux ------> <http://linux.bu.edu/>
More information about the fedora-devel-list
mailing list