[repo-coord] Re: Sub-Repo for Yum and Smart

[Axel Thimm]

On Fri, Sep 16, 2005 at 04:00:02PM +0800, Jeff Pitman wrote:
> On Friday 16 September 2005 15:37, Axel Thimm wrote:
> > > > I wouldn't mind, I would just need a copy of it in ATrpms to keep
> > > > the package set closed (and it should still build on the older
> > > > distros).
> > > >
> > > > It is also needed in a common infrastructure repo for a yum rpm.
> > >
> > > Just curious, I have been studying this some more. You provide a
> > > direct upgrade of 2.5.10 to 2.6.19 from atrpms, however, it doesn't
> > > appear that you've attempted to rectify ABI problems with the
> > > upgrade.
> >
> > There is backward ABI compatibility, which is why the major lib
> > version hasn't been bumped. If not, then upstream development would
> > had been very sloppy.
> 
> Thanks!
> 
> Right now, my approach probably deviates slightly from what you've done 
> at atrpms.  This is due to trying to keep in line with what currently 
> is done at pyvault.  I'll extract -python completely from libxml2.spec 
> and put it into libxml2-python.spec, then I'll use my buildsystem to 
> output packages for python 2.2/2.3/2.4 where needed.

That sounds awfully familiar :)

http://atrpms.net/name/libxml2-python24/

> I discussed rpm-py in a previous email.

I missed that one, what is rpm-py? google returns hits on rpm.py
instead.

> (I just released a new rpm-py that guts the configure mantra, thus,
> speeding up compile time.)  This keeps rpm at the same version as
> delivered with the distro in question.  Not sure if I want to
> upgrade this yet.

Is that perhaps the same like or similar to
http://atrpms.net/name/rpm-python/?

> Anyway, if you see ways we can continue to collaborate, let me know.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/repo-coord/attachments/20050916/3e4980d3/attachment.bin