[Please don't CC me, I'm on the list. I wish MUAs would respect the
mail-followup-to header.]
Donovan Baarda wrote:
> From archive updating point of view, my scheme has a large
> python-X.Y-foo added and a small python-foo updated when python
> upgrades. Your scheme has a large python-foo updated
Quoting Neil Schemenauer <[EMAIL PROTECTED]>:
> Donovan Baarda wrote:
> > On Sat, Sep 29, 2001 at 11:17:19PM -0700, Neil Schemenauer wrote:
> > > Donovan Baarda wrote:
> > > If you change the major or minor version of Python installed then
> > > packages that depend on it must be upgraded. There
Quoting Neil Schemenauer <[EMAIL PROTECTED]>:
> Donovan Baarda wrote:
> > Hmmm, but if only "python" can provide python-api-*, then any packages
> that
> > depend on python-api-X.Y will be broken when a new version of python
> > providing python-api-X.Z comes out, and no python-X.Y package can be
Donovan Baarda wrote:
> Hmmm, but if only "python" can provide python-api-*, then any packages that
> depend on python-api-X.Y will be broken when a new version of python
> providing python-api-X.Z comes out, and no python-X.Y package can be
> compatible with it.
That's right. Packaged modules mu
Donovan Baarda wrote:
> On Sat, Sep 29, 2001 at 11:17:19PM -0700, Neil Schemenauer wrote:
> > Donovan Baarda wrote:
> > If you change the major or minor version of Python installed then
> > packages that depend on it must be upgraded. There is no way around
> > that.
>
> Yes, but the old packages
Jérôme Marant wrote:
> Neil Schemenauer <[EMAIL PROTECTED]> writes:
> > It's easier and less error prone for packages to depend on
> > python-api-2.1 rather than "python (>= 2.1), python (< 2.2)". That's
> > it.
>
> So i don't see the need for "api" there ...
It allows people to package older
Neil Schemenauer <[EMAIL PROTECTED]> writes:
> Jérôme Marant wrote:
> > I browsed the Package file and I've seen some new things in dependencies
> > like python-api ones (similar to perl-api I guess).
> >
> > Coud you explain briefly how they work?
>
> It's easier and less error prone for
Jérôme Marant wrote:
> I browsed the Package file and I've seen some new things in dependencies
> like python-api ones (similar to perl-api I guess).
>
> Coud you explain briefly how they work?
It's easier and less error prone for packages to depend on
python-api-2.1 rather than "python (>=
On Sat, Sep 29, 2001 at 11:10:43PM -0700, Neil Schemenauer wrote:
> Carey Evans wrote:
> > By way of example, suppose I have a package "spam" that embeds Python
> > 2.1, and therefore depends on python-2.1. spam also uses the "eggs"
> > module, and therefore depends on python-eggs, which depends o
On Sat, Sep 29, 2001 at 11:31:44PM -0700, Neil Schemenauer wrote:
> Packages (mostly) conforming to this policy are at:
[...]
> - Packaged modules should depend on python-api-X.Y
>
> - Remove section on legacy versions of Python (they are
> independent). I should probably add a sect
On Sat, Sep 29, 2001 at 11:17:19PM -0700, Neil Schemenauer wrote:
> Donovan Baarda wrote:
> > First off, you need to clarify what you are attempting to achieve. There
> > are
> > three possibile aims as I see it;
> >
> > 1) single "official" version of Python in archive/distro.
> > 2) multiple a
Neil Schemenauer <[EMAIL PROTECTED]> writes:
> Zooko wrote:
> > I got some dependency errors when I tried to install:
>
> Oops, there was some dependency wierdness with python-base and that
> screwed up everything else. I've updated my Python packages. Please
> give it a try again if you don't
Packages (mostly) conforming to this policy are at:
deb http://people.debian.org/~nas woody/
I've updated a lot of packages. If there is something missing that you
use please let me know. After updating about 30 packages I'm getting
good at it. :-)
Changes from last version (off the top o
Donovan Baarda wrote:
> First off, you need to clarify what you are attempting to achieve. There are
> three possibile aims as I see it;
>
> 1) single "official" version of Python in archive/distro.
> 2) multiple alternative versions of Python in archive/distro, only one
> installed at a time.
>
Carey Evans wrote:
> By way of example, suppose I have a package "spam" that embeds Python
> 2.1, and therefore depends on python-2.1. spam also uses the "eggs"
> module, and therefore depends on python-eggs, which depends on
> python-2.1 itself.
>
> Now Python 2.2 is released, and eggs is recomp
15 matches
Mail list logo
