On Thu, Sep 05, 2002 at 08:49:21AM -0500, Dirk Eddelbuettel wrote:
On Thu, Sep 05, 2002 at 07:48:38AM -0500, Dirk Eddelbuettel wrote:
[...]
Remember, /usr/bin/python is a symlink installed by the python package,
and without a dependancy on this package there is no gaurentee that it
will
Wajig, once upon a time, compiled its .py files. That wasn't really useful as
the performance bottlenecks come from the externally called programs, not
wajig itself. So I removed that a while ago. However, the versioned Depends
and Build-Depends persisted ... and so I just got a bug report,
You should depend on exactly the Python versions you support, not on
python. For example
Depends: python1.5 | python2.1 | python2.2
I see. But why not simply Depends: python (= 1.5)
And if you dont compile any Python packages, why do you still have to
build-depend on python-dev?
Quite
On Thu, Sep 05, 2002 at 07:48:38AM -0500, Dirk Eddelbuettel wrote:
You should depend on exactly the Python versions you support, not on
python. For example
Depends: python1.5 | python2.1 | python2.2
I see. But why not simply Depends: python (= 1.5)
I think this is wrong. If this is
On Thu, Sep 05, 2002 at 07:48:38AM -0500, Dirk Eddelbuettel wrote:
You should depend on exactly the Python versions you support, not on
python. For example
Depends: python1.5 | python2.1 | python2.2
I see. But why not simply Depends: python (= 1.5)
I think this is
5 matches
Mail list logo