On 06/25/2010 01:24 PM, Nathaniel McCallum wrote:
> On 06/20/2010 05:08 AM, Robin 'cheese' Lee wrote:
>> The spec file for each per-module package I just created is generated
>> through a little and nasty script which converts spec files generated by
>> setuptools to ones complying with Fedora standards. (The script is too
>> nasty to open its source.)
>>
>> A better solution is to hack setuptools, and/or distutils, itself to
>> generate standard-complying spec files directly. But this may take some
>> time.
>
> I've attached a script called zopespec. zopespec works similarly to
> (and probably could be merged with) rpmdev-newspec. You run it and
> give it a package name. This can be zope.copy, zope-copy or
> zope-copy.spec.
>
> Given the name "zope-copy", zopespec looks up the latest version from
> pypi.python.org, downloads it and extracts a bunch of metadata. This
> metadata gets substituted into the spec that is created. It should be
> generally speaking functional, but of course the generated spec needs
> to be reviewed by a human. Let me know if you have any thoughts.
>
> Nathaniel
This script fulfills some of our basic need. But obviously we still
have much to do.
And to list the full requirements of each source package is most
important for us. Here are some suggestions:
- Our utility should also keep track of versioned requirements and
ones pulled in through the 'Extra' mechanism of setuptools.
- If setuptools is explicitly listed in requires.txt, it should not
be ignored. pkg_resources, a module provided by it, is used by modules
at runtime.
- Some packages of Python modules in Fedora are not named with
'python-' prefix, like 'pytz'. So we should have a more sophisticated
mapping from module name to Fedora package name.
Robin
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
