-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi:
Just some hints for packaging Python (iow, makes my life easier at http://python.org/pyvault).
thoughts?
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=120635 represents a number of thoughts by critically interested parties about this issue.
This request has been open for almost eighteen months now :(
Some of the respondents seem to think that only one or two macros are necessary, I still beg to differ. We need to do this once, and do it to please the widest possible audience.
A case in point is that we presently cannot migrate to Python2.4 until Zope Corporation sign off a security audit on their app server. If people didn't hard-code 2.4 into the build scripts, and if they use the include macros for C-based python code, then we could almost certainly backport any FC4 python SRPM's to our FC3 target without *any* modification required.
This is simply not the case. We've already had to manage upgrades for 2.1, 2.2, and 2.3. A lot of things associated with Fedora development are still retentive and frustrating.
Alan
On Sun, 2005-09-18 at 02:27 +1000, Alan Milligan wrote:
A case in point is that we presently cannot migrate to Python2.4 until Zope Corporation sign off a security audit on their app server. If people didn't hard-code 2.4 into the build scripts, and if they use the include macros for C-based python code, then we could almost certainly backport any FC4 python SRPM's to our FC3 target without *any* modification required.
Could you attach an FC4 spec that doesn't backport to FC3 without modification so we can see the mentioned issue?
-Toshio
packaging@lists.fedoraproject.org