Re: repo agnostic package resolvers (was: Latest apt broken?)
seth vidal <[email protected]> Wed, 19 Jan 2005 12:52:43 -0500
| Newsgroups | gmane.linux.freshrpms.user,gmane.linux.redhat.rpm.atrpms.repo-coordination |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 2005-01-20 at 01:47 +0800, Jeff Pitman wrote: > On Thursday 20 January 2005 00:13, Axel Thimm wrote: > > Works well if there are a > > handfull of them but does not scale well. Perhaps smart deals better > > with file conflicts (e.g. auto-promotes them to Conflicts:) and > > behaves better, but I haven't tested. > > Interesting RFE to be aware of: > https://bugzilla.redhat.com/beta/show_bug.cgi?id=131181 > > Implemented in 4.4. (I think; haven't tested, yet.) > > Although, maybe off-topic for this thread, but Obsoleting > directories/files eases packager's effort in determining what names > have been used before (twisted, Twisted, python-Twisted, > python-twisted) and just Obsolete the provided dir which will nuke > whatever existing packages are there. Likewise, the repo-config > packages could use similar methods in the future. (FC4+, I guess.) And yet it makes the pkg mgmt a nightmare b/c now, instead of being able to key on file name I have to go find the packages the provide that file (or worse yet, if wildcards are involved) then figure out the arch for those involved and match. oh yah - gonna be a party rewriting the obsoletes parser. -sv