Coin,
Bruce Sass [EMAIL PROTECTED] writes:
Isn't one of the objectives to reduce the number of Pythons in Debian,
so at some point not all versions will be available...
I don't think there is any reason to reduce user's liberty by forcing
them to use one specific version.
...then there are
Steve Langasek [EMAIL PROTECTED] writes:
Wow, what a constructive response. You've surely been on this list for
years and must know all the changes that need to be made to Debian's python
policy. Why didn't you reply to Bruce's original question with your own
superior write-up of this
Le mercredi 10 mai 2006 à 16:32 +0200, Marc Dequènes a écrit :
I wonder how some situations (if existing) may be solved as long as we
have unique non-versioned scripts-only packages and compiled modules
cohabiting. When for eg python2.4-soya needs editobj, it just depends on
python-editobj
Coin Joss,
Josselin Mouette [EMAIL PROTECTED] writes:
As Steve suggested, this can be solved by introducing a new variable
named ${python:Provides} in dh_python, which will read the .version as
well. Then, python-editobj will have a
Provides: python2.3-editobj, python2.4-editobj
and
Bob, Pythoners,
Em Qua, 2006-05-03 às 22:35 -0500, Bob Tanner escreveu:
I plan to add turbogears and json-py to the python-modules team; Bob,
what say you? Have you made any work on this front? Should I go on and
upload those packages to Debian?
I have most of those packages (some dated)
5 matches
Mail list logo
