Quoting Matthias Klose <[EMAIL PROTECTED]>:
> Carey Evans writes:
> > Matthias Klose <[EMAIL PROTECTED]> writes:
[...]
> Thanks. Updated in 0.3.2:
>
> http://ftp-master.debian.org/~doko/python/
Nice work updating Neil's policy. I'd be interested to hear Niels comments now
that he is back.
Quoting Matthias Klose <[EMAIL PROTECTED]>:
> Donovan Baarda writes:
> > Good point... I'd forgotten about that. This means we might as well go
> > strait to python2.1 as the default, but make sure that the
> python2.1-xxx
> > packages have versioned conflicts with all the packages that depend on
Quoting Jérôme Marant <[EMAIL PROTECTED]>:
> Matthias Klose <[EMAIL PROTECTED]> writes:
>
> > Jérôme Marant writes:
> > > I do propose that we install all architecture independant modules
> > > in /usr/share and all architecture dependent modules in /usr/lib
> > > as it has always been.
[..
On Sun, Oct 21, 2001 at 10:58:01PM +1300, Carey Evans wrote:
> Donovan Baarda <[EMAIL PROTECTED]> writes:
>
> (Actually 60, but gimp-python also depends on python-base (<< 1.6.0)).
>
> Packages that depend on python:
>grep-dctrl -FDepends -e 'python([ ,]|$)' Packages
I maintain one of those
Matthias Klose <[EMAIL PROTECTED]> writes:
> Carey Evans writes:
>
> > Another possibility is for python-base to go away, and for a new
> > package that conflicts with it, and has a different name, to take its
> > place.
>
> basically that is Neil's proposal of a python-api package.
I thought p
On Thu, Oct 18, 2001 at 07:25:04PM +0200, Matthias Klose wrote:
> hmm, seems I've been kicked of the debian lists. anyway, could you
> implement the scripts for your c) proposal? would it be a good idea to
> put the debian directories under CVS control, so we have access to it?
And I thought perha
Matthias Klose <[EMAIL PROTECTED]> writes:
> Jérôme Marant writes:
> > I do propose that we install all architecture independant modules
> > in /usr/share and all architecture dependent modules in /usr/lib
> > as it has always been.
>
> assume we have a package with an architecture independ
Donovan Baarda writes:
> Good point... I'd forgotten about that. This means we might as well go
> strait to python2.1 as the default, but make sure that the python2.1-xxx
> packages have versioned conflicts with all the packages that depend on just
> python or python-base and install into /usr/lib/
Jérôme Marant writes:
> I do propose that we install all architecture independant modules
> in /usr/share and all architecture dependent modules in /usr/lib
> as it has always been.
assume we have a package with an architecture independant module and
an architecture dependent module. Then we
Hi,
Since no mass uploads have happened yet, I think it is still worth
changing the following.
I do propose that we install all architecture independant modules
in /usr/share and all architecture dependent modules in /usr/lib
as it has always been.
This won't break anything since th
Carey Evans writes:
> Donovan Baarda <[EMAIL PROTECTED]> writes:
>
> > Good point... I'd forgotten about that. This means we might as well go
> > strait to python2.1 as the default, but make sure that the python2.1-xxx
> > packages have versioned conflicts with all the packages that depend on just
Donovan Baarda writes:
> On Sun, Oct 21, 2001 at 10:27:54AM +1300, Carey Evans wrote:
> > Matthias Klose <[EMAIL PROTECTED]> writes:
> >
> > [...]
> >
> > > exactly. But you see that these packages will break when you try to
> > > upgrade. We can't make 2.1 the default right now, because we will
Carey Evans writes:
> Matthias Klose <[EMAIL PROTECTED]> writes:
>
> [...]
>
> > 2.4. Dependencies
> > -
> >
> > Packaged modules must depend on `python-base (> .)' and
> > `python-base (<< .)'.
>
> (>= .), right?
>
> Shouldn't this explain just what . is? I assume i
Donovan Baarda <[EMAIL PROTECTED]> writes:
> Good point... I'd forgotten about that. This means we might as well go
> strait to python2.1 as the default, but make sure that the python2.1-xxx
> packages have versioned conflicts with all the packages that depend on just
> python or python-base and i
On Sun, Oct 21, 2001 at 10:27:54AM +1300, Carey Evans wrote:
> Matthias Klose <[EMAIL PROTECTED]> writes:
>
> [...]
>
> > exactly. But you see that these packages will break when you try to
> > upgrade. We can't make 2.1 the default right now, because we will
> > _silently_ break packages. Before
15 matches
Mail list logo
