--=-fcls/KwsHgWYD2MVzLDa Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi all, So I looked at the possiblity of backporting the comps.xml stuff to python1.5.2 ahahahahah - fat chance. so I think I'm going to shelve comps.xml for yum 1.0 - and work on closing out stuff on this branch. then the devel branch should begin. Stuff for the stable branch to have implemented before it closes: 1. would LOVE to get yum -c http://url/to/conf/file but there is one problem: Configparser requires a file name - not a filehandle to parse and python does not, currently, have a mkstmp. I don't want to get into a potential race condition/security problem with a tmp file. I'm open to ideas, though. 2. would like to stabilize/finalize what people would like yum update vs yum install to do - this vis-a-vis the discussion from last week that that Connie brought up. 3. Make the other cron job (the yum clean once a week/month) - this is trivial 4. implement reget support that was sent in. Stuff I'd like to discuss for the devel branch: 0. setup a public cvs server 1. redo of some of the nevral to include file:// url support 2. fix up/deal with/make saner urlgrab 3. make it i18n compliant - so we could use different log stuff - I'm going to have to figure out how to do this first :) I don't think it's terribly hard but I don't know how to do it. 4. Make the rpm callbacks prettier 5. make yum-arch more intelligent about which headers it makes new -I don't know if this will speed it up at all, but its worth a shot 6. determine if rpm 4.1 will require a complete rewrite or just most of a complete rewrite. 7. determine if redhat-config-packages and its accompanying modules obsoletes the need for yum at all :) - or at the very least if it would be the easiest route to follow to wrap the modules provided there. 8. comps.xml integrated - I like the comps.xml layout a lot. 9. a nifty web interface for groups of machines 10. maybe a daemon that runs and polls for updates throughout the day - no more reliance on cron :) 11. python 2.2 requirement 12. I'd love to see a graphical interface but I'm going to have to learn how to do that first :) 13. split apart and reorganize the functions in clientStuff and serverStuff - they've been a grab bag for a while now I think thats all I can think of for the moment - can anyone remember anything else? thanks -sv --=-fcls/KwsHgWYD2MVzLDa Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA9av1c1Aj3x2mIbMcRAlDhAJ9ddbyMonqLBqnhdZnP/tHe9lCSfACcDHYe ACDcdnEWcpSQ3eRjQbOixBo= =lAeA -----END PGP SIGNATURE----- --=-fcls/KwsHgWYD2MVzLDa--
