Ralph Giles writes:
> On Sun, Apr 03, 2005 at 03:44:47PM +0200, Matthias Klose wrote:
>
> > no, because you cannot assure, that all modules installed in one
> > version are installed on the other version as well.
>
> So because debian packages don't track python module dependencies
> correctly,
Ralph Giles writes:
> On Sun, Apr 03, 2005 at 08:54:58PM +0200, Matthias Klose wrote:
>
> > > > no, because you cannot assure, that all modules installed in one
> > > > version are installed on the other version as well.
> > >
> > > So because debian packages don't track python module dependencie
On Sun, Apr 03, 2005 at 08:54:58PM +0200, Matthias Klose wrote:
> > > no, because you cannot assure, that all modules installed in one
> > > version are installed on the other version as well.
> >
> > So because debian packages don't track python module dependencies
> > correctly,
>
> incorrect
On Sun, Apr 03, 2005 at 09:21:55PM +0200, Matthias Klose wrote:
> consider
>
> Package: baz
> Depends: python2.2 | python2.3, python2.2-foo | python2.3-foo,
> python2.2-bar | python2.3-bar
>
> the dependencies are fullfilled installing python2.2-foo and python2.3-bar...
So how does package
On Sun, 2005-04-03 at 12:53 -0700, Ralph Giles wrote:
> On Sun, Apr 03, 2005 at 09:21:55PM +0200, Matthias Klose wrote:
>
> > consider
> >
> > Package: baz
> > Depends: python2.2 | python2.3, python2.2-foo | python2.3-foo,
> > python2.2-bar | python2.3-bar
> >
> > the dependencies are fullf
5 matches
Mail list logo
