On 12/6/05, Matthew Miller mattdm@mattdm.org 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?
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.
-jef