On Mon, Apr 09, 2007 at 01:35:09PM +0200, Josselin Mouette wrote:
> Le lundi 09 avril 2007 à 12:32 +0200, Francesco Paolo Lovergine a
> écrit :
> > Package: python-support
> > Version: 0.6.3
> > Severity: important
> >
> > While working on thuban I used this control file:
> >
> > http://svn.debian.org/wsvn/pkg-grass/packages/thuban/trunk/debian/control?op=file&rev=0&sc=0
> >
> > introducing the alternative field
> >
> > Python-Depends: python-wxgtk2.6 (>= 2.6.3), python-sqlite (>= 0.4),
> > python-xmlbase
>
> > Note that it depends on ALL alternative versions for 2.4 and 2.5 -
> > which are the pyversions I declared (2.4-).
> > It should depend in OR from those alternatives, not requiring the
> > installation of all damn per-python version modules AFAIK.
>
> This is expected. The per-python version are virtual packages which have
> to be provided by the packages you depend upon. This doesn't mean, in
> your example, that python2.4 and python2.5 will be brought, only that
> python-wxgtk2.6 and so on have to provide the python2.5 interfaces.
>
Sigh, I understand it is expected, but I find it ugly. If someone would
use just one single python version has to install tons of packages for
all other versions too. In the specific case I have to install also both
2.4 and 2.5 editions for every modules the program use. I know it does
not require installation of all python interpreters too, but it does not
make me feel better :)
> If you don't do that, the Provides: field is meaningless. This was
> discussed at large in Oaxtepec. Note that you don't need to use
> Python-Depends if you don't have a "Provides: ${python:Provides}", but
> it is recommended.
>
So I have definitively to use Python-Depends even if the program
deos not provide public modules/extensions? Is that documented?
> > For instance in this case:
> >
> > python2.5-wxgtk2.6 | python-wxgtk2.6
> > python2.5-xmlbase | python-xmlbase
> > python2.5-sqlite | python-sqlite
>
> These dependencies would be semantically wrong.
>
--
Francesco P. Lovergine
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
