On Mon, 10 Dec 2012, Colin Guthrie wrote: > > > Maybe instead of obsoleting packages, task-obsolete could conflict with > > those packages : > > Could it obsolete *and* conflict packages and get the best of both > worlds? If that was the case it should work both from a UI level and > also from a structural (i.e. repository) level. > > If that works, then we just define a simple macro at the top of the spec > and use it throughout: > > %kill foo > %kill wibble > > etc. which automatically adds both the conflicts and the obsoletes tags.
I don't know what urpmi/rpmdrake is doing when there is both a conflict and an obsolete. If it is doing the same as what we have now with only obsolete, but with a warning, it looks like a good idea.
