Packaging distutils2 for Fedora

The spec file, is attached and lack many things. I also need to add files like README, COPYING etc.

The problem is, after installtion of the generated rpm, "python -distutils2-1.0-0.1.0.a3.fc16.noarch.rpm" 
, distutils2 functionalities (such as pysetup) are still not available in the system, though I could find the distutils2 module in the interpretor

Please guide, for the necessary changes/modifications, and I hope to see this package soon in Fedora repository

this is my first packaging initiative

Regards
Vikash Agrawal

Hi Vikash - thanks for working on this.

It's normal when packaging code "downstream" for Fedora to file a package review request at bugzilla.redhat.com, following the process here:

http://fedoraproject.org/wiki/Package_Review_Process

(sorry if the process seems byzantine; I can help if need be).

I just a did quick search and didn't see one for distutils2 there.

Some immediate things struck me about the specfile:
* it's normal to linewrap the %description clause (the specfile should be readable in a 80-column display)
* you don't need the CFLAGS= stuff for a noarch package

As for the question about things like "pysetup" not being available - are these meant to end up in /usr/bin ?  If so, this may indeed be an issue for upstream distutils2 (and hence for this bug tracker).

Hope this is helpful
Dave

Thanks for your support of distutils2, but this tracker is the wrong place for this bug tracker, as no RPM spec file will be added to the distutils2 repo.  If there are bugs in distutils2 that prevent you from making a RPM, please say so, otherwise I will close this report (but stay available via private email or the distutils-sig mailing list).

hi merwok, 
I didn't know this is the right place for that bug/query. I am still in the process of learning packaging, and at this moment I wont be able to tell that if its a problem of distutils2 or not, though I do feel that pysetup should have installed directly, considering my spec file is correct.

So as o now, the bug is closed, and later I will come with concrete results.

I will be available via private email and I will discuss this issue with dmalcolm over IRC