Tim Lauridsen wrote:
seth vidal wrote:
On Fri, 2007-07-13 at 10:00 +0200, Tim Lauridsen wrote:
Now that cfgparse has been resurrected and renamed to iniparse [1], how
do we handle it.
1. Include it in the yum code as a iniparse module.
2. submit it for Fedora as a separate package and add it as a dependency
(It could be useful for other projects).
Let me know what you think.
2
Ok, i will do the following:
1. Create a spec file and get it includes upstream [Done]
2. Wait for upstream to do a release. ( Sometime next week)
3. Submit for inclusion in Fedora.
4. built it for (F7, Rawhide, EPEL).
5. Added to yum.spec as a requirement and make it use
compat.ConfigParser from iniparse, insted of default ConfigParser.
Does it make sense.
Tim
iniparse-0.2 has now been released upstream [1] (Thanks to Paramjit
Oberoi for his great work).
I have submitted it for package review in Fedora[2].
Tim
[1] : http://code.google.com/p/iniparse/
[2] : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248991
_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
