[Yum-devel] Goal-like things for next few months

Tim Lauridsen tim.lauridsen at googlemail.com
Wed Aug 26 12:03:24 UTC 2009


On 08/25/2009 10:17 PM, Seth Vidal wrote:
>
> Following up on some of these 10 months down the road:
>
>
> On Thu, 13 Nov 2008, Seth Vidal wrote:
>
>> A set of things I want to work on as Fedora starts into the F11 cycle.
>>
>> Things followed by question marks are questionable.
>>
>> Yum:
>> - keyword metadata searching/tag browsing
>
> In the works - contigent on the metadata being available - eta 
> Fedora13 timeline
>
>> - db to store yum-specific info about packages - barring that rpm 
>> doesn't
>> end up letting us do this?
>
> Done - yumdb in current yum versions.
>
>> - merge yum-complete-transaction into yum instead of yum-utils.
>
> not done - should it still be?
if yum-utils is installed as default (as in Fedora), there is no die 
hard reason to merge it into base IMHO.
>
>> - Think about different mechanisms for multiple provider handling:
>>      - James' metadata code
>>      - Optional prompting for selecting providers??
>
> Not done - but still worth considering - well - maybe not the prompting.
>
>> - downgrade?
> done - more or less - filled with potential errors that downgrades 
> always have but for the simple cases this works.
>
>> - repomd.xml signature checking as default
>
> not as default - but in Fedora 12 it is enabled and seems to be working.
>
>> - merge yum-security plugin/update_md functions into base?
>
> Do we want to? the update_md functions are in base - just accessing 
> them is not. updateinfo.xml files are still not terribly common in repos.
The update metadata handling basics should be in base, the options added 
by yum-security is not needed to go into
base IMHO.
>
>
>> - merge in post-transaction-action?
>
> it's in yum-utils - but probably not a good plan to merge it into yum 
> in general anymore.
Agree
>
>> - trusted keys per repo?
>
> still not done - ultimately waiting on different code in rpm-python/rpm.
>
>
>
> so not terrible results. Some are blocking on other pieces first, of 
> course.
>
> Where do we go from here:
>
> yum history - a history db of what transactions were run and what the 
> system looked like before it was run - not really for rollbacks but 
> more for an audit trail.
Sounds like a great idea
>
> multi-file transfer - now that python-urlgrabber is using pycurl it is 
> probably time to start sorting out how to do multifile transfer at the 
> same time. It would at least allow us to download a bunch of repodata 
> at the same time. The interface for the user will be the "interesting" 
> part here. Still lots of work to go on.

Good idea, but fears the user interface too :)

>
>
> documentation - I think we've added a lot of not-so-well-known 
> features in the last year or so - it's probably worth talking them up 
> a bit so people know of new things yum can do, now.
Yes, we need to promote all the new great stuff, many people don't know 
about

Tim


More information about the Yum-devel mailing list