[Pkg-fonts-devel] Questions regarding a package that creates a python module (written in C)

[Jakub Wilk]

* Rogério Brito <rbrito at ime.usp.br>, 2010-05-27, 06:11:
>>>With that said, what is the recommended course of action? Should I 
>>>manually build the package twice in a row in debian/rules telling it 
>>>first to configure with python 2.5 and then 2.6
>>Yes. Please don't hardcorde version numbers in debian/rules, however; 
>>use `pyversions -r` to query which Python versions are supported.
>
>Right, right. I am against hardcoding anything, in principle. :-)
>
>> >or is there any solid, recommended approach to this problem (which
>> >I am sure should appear in many other packages that provide python
>> >modules written in C)?
>>
>> For distutils-based build systems (i.e., not for fontforge), dh(1)
>> builds modules for all supported Python versions (almost) out of the
>> box.
>
>So, summarizing, this would mean that I would have to force feed the
>configure script of fontforge for each python version, if I understood
>it correctly?

Sometimes Python modules are only a tiny bit of the codebase and 
building everything twice would be wasteful. E.g. it looks like that for 
fontforge it should be enough to run "$python setup.py build" and 
"$python setup.py install" for each supported $python.

-- 
Jakub Wilk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20100527/657d315e/attachment.pgp>