Re: [Yum-devel] iniparse (was: cfgparse)

2007-07-20 Thread Tim Lauridsen
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

Re: [Yum-devel] iniparse (was: cfgparse)

2007-07-15 Thread Tim Lauridsen
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

Re: [Yum-devel] iniparse (was: cfgparse)

2007-07-15 Thread Debarshi 'Rishi' Ray
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

Re: [Yum-devel] iniparse (was: cfgparse)

2007-07-13 Thread seth vidal
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