Re: Updated experimental packages

2001-09-07 Thread Neil Schemenauer
Gregor Hoffleit wrote: > Note that the python2 packages are, at this time, legacy. Okay. What do you think about my plan to have "python" be the latest version of Python and then have "python-x.y" packages for those people who need to have older versions? Neil

Re: Updated experimental packages

2001-09-07 Thread Gregor Hoffleit
* Neil Schemenauer <[EMAIL PROTECTED]> [010907 00:33]: > I see now that the python2 packages made it into unstable. This is a > mistake IMHO. The Perl guys tryed this and it didn't work. Also, the > name should have been python2.1 not python2. What problem does naming > the packages "python2" s

Re: Updated experimental packages

2001-09-07 Thread Sergio Talens-Oliag
El Fri, Sep 07, 2001 at 12:08:20PM +0200, Mikael Hedin escribió: > Neil Schemenauer <[EMAIL PROTECTED]> writes: > > [...] > > Looks fint to me! > > > I'm willing to build new version of packages with broken dependencies. > > Can we handle the upgrade from Python by having a long list of conflict

Re: Updated experimental packages

2001-09-07 Thread Mikael Hedin
Carey Evans <[EMAIL PROTECTED]> writes: > My preference would be for virtual packages named "python-x.y" to be > the target of the dependency. This seems to me to allow _more_ > flexibility, since _any_ package can then provide the dependency, even > if it can't be named "python" for whatever rea

Re: Updated experimental packages

2001-09-07 Thread Mikael Hedin
Neil Schemenauer <[EMAIL PROTECTED]> writes: [...] Looks fint to me! > I'm willing to build new version of packages with broken dependencies. > Can we handle the upgrade from Python by having a long list of conflicts > in the "python" package? Something like: > > Conflicts: python-some-ext

Re: Updated experimental packages

2001-09-06 Thread Carey Evans
Neil Schemenauer <[EMAIL PROTECTED]> writes: > I see now that the python2 packages made it into unstable. This is a > mistake IMHO. The Perl guys tryed this and it didn't work. Also, the > name should have been python2.1 not python2. What problem does naming > the packages "python2" solve? It

Updated experimental packages

2001-09-06 Thread Neil Schemenauer
I see now that the python2 packages made it into unstable. This is a mistake IMHO. The Perl guys tryed this and it didn't work. Also, the name should have been python2.1 not python2. What problem does naming the packages "python2" solve? It seems like a big pain for everyone for no gain. I've