Re: Manual package check and example
Le mardi 27 juin 2006 à 12:22 +0900, Kai Hendry a écrit : > sam$ lintian webpy_0.138-2_i386.changes > W: webpy source: build-depends-without-arch-dep python-support > W: webpy source: build-depends-without-arch-dep python-dev > W: python-webpy: script-not-executable > ./usr/share/python-support/python-webpy/web.py > > I can't recall what's going on with this "build-depends-without-arch-dep". Can > it be ignored? This is because lintian thinks they should be put in Build-Depends-Indep. For python-support this is true, but for python-dev the warning should be ignored as you're using it in the clean target. -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
RFS: templayer -- layered template library for Python
Hi all, Would anyone be able to sponsor templayer? It is a python module that I need for urwid in order to be able to generate the tutorial. It uses cdbs and python-support for building at the moment. dget http://mentors.debian.net/debian/pool/main/t/templayer/templayer_1.2-2-1.dsc http://mentors.debian.net/debian/pool/main/t/templayer/templayer_1.2-2-1.diff.gz http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=templayer lintian/linda/cowbuilder clean and so on. The Replaces/Conflicts/Provides are for users of the upstream packages. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
installation of scripts in the brave new Python world
Hello All: As I was trying to implement the new Python policy, I noticed an effect which is not directly addressed in the policy. That is when a package contains modules and scripts, there have to be special precautions taken to make sure that the scripts are not installed with a first line of #!/usr/bin/pythonX.Y instead of #!/usr/bin/python The python-imaging package, which has been given as an example of using pycentral fixes this by using sed to correct all first lines in scripts. This is easily done because all the scripts have file names of the form *.py. If a script does not have this kind of filename, it is more difficult. Here is another suggestion for accomplishing the same thing. The idea here is to just build and install the scripts a final time using he default python after the scripts have already been installed from the versioned python installs. PYVERS=$(shell pyversions -vr) build-python-all: $(PYVERS:%=build-python%) python setup.py build_scripts --build-dir=build/Scripts || exit 1; touch $@ build-python%: dh_testdir python$* setup.py build || exit 1 ; touch $@ install-python-all: $(PYVERS:%=install-python%) python setup.py install_scripts --force \ --install-dir=$(CURDIR)/debian/debian/python-foo/usr/bin \ --build-dir=build/Scripts || exit 1 ; install-python%: python$* setup.py install \ --prefix=$(CURDIR)/debian/python-foo/usr || exit 1 ; -find $(CURDIR)/debian/ -name '*.py[co]' | xargs rm -f Cheers, Carlo -- Carlo U. Segre -- Professor of Physics Associate Dean for Special Projects, Graduate College Illinois Institute of Technology Voice: 312.567.3498Fax: 312.567.3494 [EMAIL PROTECTED]http://www.iit.edu/~segre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: installation of scripts in the brave new Python world
On 6/27/06, Carlo Segre <[EMAIL PROTECTED]> wrote: Hello All: As I was trying to implement the new Python policy, I noticed an effect which is not directly addressed in the policy. That is when a package contains modules and scripts, there have to be special precautions taken to make sure that the scripts are not installed with a first line of #!/usr/bin/pythonX.Y instead of #!/usr/bin/python (...) How it's that different than patch the source packages to s/python2.4/python/ as we do actually in some cases or replacing to python2.3 when it isn't 2.4 compatible code? regards, -- stratus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: installation of scripts in the brave new Python world
On Tue, 2006-06-27 at 20:22 -0300, Gustavo Franco wrote: > On 6/27/06, Carlo Segre <[EMAIL PROTECTED]> wrote: > > > > Hello All: > > > > As I was trying to implement the new Python policy, I noticed an effect > > which is not directly addressed in the policy. That is when a package > > contains modules and scripts, there have to be special precautions taken > > to make sure that the scripts are not installed with a first line of > > > > #!/usr/bin/pythonX.Y > > > > instead of #!/usr/bin/python > > > > (...) > > How it's that different than patch the source packages to > s/python2.4/python/ as we do actually in some cases or replacing to > python2.3 when it isn't 2.4 compatible code? distutils rewrites scripts at installation time. Patching the source package will not work. http://docs.python.org/dist/node10.html -- Joe Wreschnig <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
