Hello,
since I have read [0], I'm migrating to python-support for the new
version of my python-shapely package.
But I admit that in the followups of the said mail, I got somehow
confused... the 3 lines that Piotr suggests to add:
| if [ $1 = upgrade ] dpkg --compare-versions $2 lt 1.2.3-4; then
[Pietro Battiston, 2009-05-29]
since I have read [0], I'm migrating to python-support for the new
version of my python-shapely package.
But I admit that in the followups of the said mail, I got somehow
confused... the 3 lines that Piotr suggests to add:
| if [ $1 = upgrade ] dpkg
Package: wnpp
Severity: wishlist
Owner: Stefano Zacchiroli z...@debian.org
* Package name: python-repoze-tm2
Version : 1.0a4
Upstream Author : Agendaless Consulting repoze-dev at lists repoze org
* URL : http://pypi.python.org/pypi/repoze.tm2/
* License :
Package: wnpp
Severity: wishlist
Owner: Stefano Zacchiroli z...@debian.org
* Package name: python-toscawidgets
Version : 0.9.4
Upstream Author : Alberto Valverde Gonzalez alberto at toscat net
* URL : http://toscawidgets.org/
* License : MIT/X
Programming
Package: wnpp
Severity: wishlist
Owner: Stefano Zacchiroli z...@debian.org
* Package name: python-webflash
Version : 0.1a9
Upstream Author : Alberto Valverde Gonzalez alberto at python-rum org
* URL : http://python-rum.org/wiki/WebFlash
* License : MIT/X
Package: wnpp
Severity: wishlist
Owner: Stefano Zacchiroli z...@debian.org
* Package name: python-repoze-what
Version : 1.0.8
Upstream Author : Gustavo Narea repoze-dev at lists repoze org
* URL : http://www.repoze.org/
* License : BSD-derived
Package: wnpp
Severity: wishlist
Owner: Stefano Zacchiroli z...@debian.org
* Package name: python-repoze-what-pylons
Version : 1.0
Upstream Author : Gustavo Narea repoze-dev at lists repoze org
* URL : http://pypi.python.org/pypi/repoze.what-pylons/
* License :
Hi Kov and Bob,
in the process of packaging Python modules that are needed for
TurboGears 2, I've stumbled upon the pkg-turbogears alioth project
[1], which looks like dead: not even turbogears 1 dependencies are
there and is inactive since 2006.
Can you confirm that?
Also, it looks like
Hello,
What is the correct umbrella to package a plugin for a Python
application under? DPMT or PAPT?
And, is there some recommended binary package naming scheme for such
packages?
I am asking those questions, because I intend[1] to package hg-git[2],
a plugin for Mercurial (maintained by
Package: wnpp
Severity: wishlist
Owner: Stefano Zacchiroli z...@debian.org
* Package name: python-repoze.who
Version : 1.0.13
Upstream Author : Agendaless Consulting repoze-dev at lists repoze org
* URL : http://www.repoze.org/
* License : BSD-derived
Jakub Wilk escribió:
Hello,
Hi Jakub,
What is the correct umbrella to package a plugin for a Python
application under? DPMT or PAPT?
PAPT, since it's not a module
And, is there some recommended binary package naming scheme for such
packages?
Nope, there's only one for modules, but that
Emilio Pozuelo Monfort po...@ubuntu.com writes:
Jakub Wilk escribió:
What is the correct umbrella to package a plugin for a Python
application under? DPMT or PAPT?
PAPT, since it's not a module
Hmm? I can't see a reasonable way to package a Python application
plug-in that *isn't* a
12 matches
Mail list logo
