[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#118916: wajig: should depend on python, not python-base



  "Matthias" == Matthias Klose <doko@cs.tu-berlin.de> writes:
  >> * Adapted Python Policy (as of version 0.3.7) * debian/control: Depends
  >> python (>= 2.1), python (<< 2.2) (Closes: #118916) * debian/control:
  >> Added Build-Depends on python2.1-dev (Closes: #19009)
  >> 
  >> -- Dirk Eddelbuettel <edd@debian.org> Sat, 10 Nov 2001 20:18:38 -0600
  Matthias>  I didn't look at the new source, but build-depending on
  Matthias> python2.1-dev means that you have to call python2.1 during the
  Matthias> build. `python' may point to something else, if we change the
  Matthias> python version to 2.2. So either build-depend on python (>= 2.1),
  Matthias> python (<< 2.2) or use `python2.1'.

I still don't get it. What is the difference?  python2.1 vs python2.1?
Further, Python Policy states 

     You should not make a default, unversioned module package
     `python-<foo>' depend on the versioned Python package `python<X>.<Y>'!

     The source package must declare

          Build-Depends: pythonX.Y-dev

     where <X>.<Y> is the version used in the `Depends'.

so python2.1 would be out of the picture as per the first cited paragraph.

Can you enlighten me?

Dirk


-- 
Better to have an approximate answer to the right question 
than a precise answer to the wrong question. -- John Tukey



Reply to: