[Yum-devel] yum devel stuff - tasks that need some thinking and doing.
seth vidal
skvidal at phy.duke.edu
Tue Jun 22 20:20:41 UTC 2004
Hi all,
some things that could take some initiative and good minds to come up
with neat ways of doing them. A lot of these can occur independent of
yum, except they should be against the HEAD cvs tree. As many of these
that could be independent modules that yum can import and use would be
best.
Things high-ish on the priority lists:
- sorting out the install package cli parsing (mine, and pain) :)
- building dep tree up properly.
- pre,post, pre-trans,post-trans stuff that was on yum-devel earlier
this month - that object would be a good, independent place to work.
- yum-queue code
- draw up framework for doing yum-source install
- maybe write up a separate downloader independent of yum for packages
in yum repos - so use the modules in yum to parse the metadata but not
include the downloader as a sub-command from the yum executable. but as
it's own executable yum-download foo-1.1-1.i386 (for example)
- expand out the yum querying concepts for the new metadata - more or
less new ways of querying and mining the metadata for more information
most of these are add-ons but they are things I'd like to have out
there. But ideally, NOT in the yum-command itself.
- hell a yum-command template for doing $some task, heck something
using python -i and outputting things to be added would be kinda cool,
too. Equivalently, making a yum shell using the python interactive shell
(do-able, I think)
- test units for most of the cli parsing code
-sv
More information about the Yum-devel
mailing list