If the policy is "whatever works", then my patches comply with the Mandriva policy (in other words, they cause bdist_rpm to generate specfiles pursuant to the policy) and there is no need to discuss this any further.
Show them to me and I will rewrite my patches to accomodate them.
> Again, put the patch logic in an extension called from a commandline
My patches do not touch core distutils. Stop lying about my work.
> Yes, there is. Mandriva naming is whatever will work in a spec file.
The core of the issue is simple:
* As of today, bdist_rpm generates invalid spec files when supplied with a pre-release python package (egg or standard distutils one). What I mean is that it generates RPMs that would UPGRADE final releases. Which is broken behavior.
Now, onto this discussion itself -- let's go meta:
I have had enough of your lies and misrepresentations. Now, you had your chance to make a case as to why my patches break anything in Mandriva, and I have conclusively shown they do not break anything there. You have had plenty of chances to make your case, present examples, show code, improve the patches, one-up my work in MANY WAYS.
Alas, you haven't done any of that -- all you did was complain about "policy" -- and, frankly, I have worked very hard to make this work and I do not appreciate you chiming in with pointless bitching that has no basis in engineering reasons.
So further mails from you will be directed to /dev/null.
Manuel Amador (Rudd-O) <firstname.lastname@example.org>
Now playing, courtesy of Amarok: DJ Jürgen presenting Alice Deejay - Better off alone (club vocal mix)