I have a silly little problem with getting Python's distutils to play nice with Debian packaging. The library I am packaging (PyGGy) has a few python files that double as executable scripts (in short they have '#! /usr/bin/python' at the top of the file, while still being part of a library, and they are executable, I am sure you know what I mean ;-). Distutils insists on leaving them non-executable after a './setup.py build'. However, since they contain that first line lintian complains that they are scripts, but non-executable: W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/dfa.py N: N: This file starts with the #! sequence that marks interpreted scripts, N: but it is not executable. N: W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/dot.py W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/lexer.py W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/nfa.py W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/pyggy.py W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/pylly.py W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/slrgram.py W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/srgram.py W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/util.py Do I leave it them the way they are, or is there a nice way of resolving this? /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus@therning.org http://magnus.therning.org/ Finagle's Second Law: Always keep a record of data -- it indicates you've been working.
Attachment:
signature.asc
Description: Digital signature