Le samedi 31 mai 2008 à 22:00 +0200, Manuel Prinz a écrit : > I have a Python application with private extension modules, so the package is > Arch: any. Because there is no way (at least I'm not aware of that) to split > the package because the modules are private, I can't seperate the large part > of the app out to /usr/share/package/ because the extension module parts > under /usr/lib/package/ can't be loaded. Is there a way to do that or is the > recommended way to put everything to /usr/lib/package/ even thought large > parts are arch-indep? At least, current practice in this case is to put everything in /usr/lib. > Also, is it OK to build just against the default Python version in Debian or > should all versions be supported? Upstream's build system does not enable to > build against a specific version of Python. For private extensions, it is quite complex to support multiple python versions as you need a specific rtupdate script, so in general you should not do that. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `- our own. Resistance is futile.
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=