Re: Sub-Repo for Yum and Smart
Jeff Pitman <[email protected]> Fri, 16 Sep 2005 16:00:02 +0800
| Newsgroups | gmane.linux.redhat.rpm.atrpms.repo-coordination |
|---|---|
| Message-ID | <[email protected]> |
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. I discussed rpm-py in a previous email. (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. Anyway, if you see ways we can continue to collaborate, let me know. -- -jeff