Feature Proposal: Use cases database

[Les Mikesell]

Richard Hughes wrote:
> On Wed, 2008-09-10 at 01:23 -0500, Les Mikesell wrote:
>> Even better than talking about it would be creating the exact package 
>> lists that best enable a variety of use cases and a handy way of
>> telling yum/packagekit to duplicate them on your machine.  Then anyone
>> else who needed to do the same thing would have a push-button choice.
>> The idea should be that anyone could 'publish' their installed package
>> set and describe why they think it is best for a particular use, and
>> anyone who was convinced by their description/reputation, etc. could
>> just clone that setup.
> 
> PackageKit already supports catalogs, which is pretty much what you
> describe.
> 
> Have a look here http://www.packagekit.org/pk-faq.html#catalogs and tell
> me if that does what you need.

That's the easy half of the job.  What I want is a tool where someone 
who has added 3rd party repositories, then added/removed any number of 
packages from any source can push a button and have the catalog 
generated that would reproduce that set of packages on any other machine 
starting with the same base distro version.   Someone setting out to 
assemble the perfect set of tools for a job won't know if they've 
succeeded until after they've tried a lot of the wrong ones, and after 
they have their system working perfectly they probably won't start over 
to build a catalog.  I want something that will deduce what's there and 
where it came from after the fact and does everything necessary to 
reproduce it.   Ideally, I'd also like it to give you a choice of 
duplicating the exact versions of all the packages on the copy or 
floating them all to the current update.

-- 
    Les Mikesell
     lesmikesell at gmail.com