El Miércoles 11 Marzo 2009, Gerry Reno escribió:
Ok, Mandriva comes to mind. It's policy is different and allows
more
flexibility than Fedora's.
Well, would you be so kind to link the Mandriva policy for us to read about
it?
Besides, policies are meant for humans. And policies change. We don't
need distro policies hard-coded into Distutils. That makes for brittle
code.
So what you're saying, in effect, translates to "sorry, man, you cannot build
your Plone packages for RPM distributions, nor can anybody else build any sort
of pre-release eggs either". Well, sorry, man, that's not acceptable.
Why? A distro's policy is defined for 'human' behavior
for users of
that distro. Users of distro X should not be hostage to policies of
distro Y. 'version' and 'release' should be formatted by humans for
whatever distro is the target. There should be no enforcement of any
distro's 'packaging policy' over the fields.
Policy schmolicy, the current distutils behavior builds pre-release RPMs that
UPGRADE final release packages, which is broken and stupid because distutils
ought to be taking care of the impedance mismatch between python-style
versioning and RPM-style lexicographical versioning, but it doesn't. I have a
solution that works in fedora, rhel and centos, and likely works just as well
on other RPM distros including Mandriva and SUSE. Do you have an alternative
solution? No? Then let's stop discussing this because what you're saying
sounds like a baseless complaint on the grounds of abstract pureness instead
of practical results.
Regards,
Gerry
--
Manuel Amador (Rudd-O) <rudd-o(a)rudd-o.com>
Rudd-O.com -
http://rudd-o.com/
GPG key ID 0xC8D28B92 at
http://wwwkeys.pgp.net/
Excellent day to have a rotten day.