Il gio, 2002-07-25 alle 21:20, Matthias Klose ha scritto:
> some packages do have problems to built with 2.2 (packages which are
> not updated for a loong time ...)
do we need them in sarge? if they can't be ported to 2.2/2.3 upstream
maybe they are not maintained. and if they are not maintained (and we
don't need them) they can simply go.
> My current plan is:
>
> - upload python2.3 packages soon (when 2.3alpha1 is released)
yesss!
> - remove python1.5 from unstable
and all packages depending on it. right.
> - adopt python-central for 2.1, 2.2 and 2.3, hopefully with the
> help of the author, hint, hint
>
> - upload python2.3 beta to unstable
>
> - make it the python default
>
> - remove python2.1 from unstable
please, gime some months to make the transition.
> I don't see much sense in making the switch to 2.2 now and then again
> to 2.3. But anyway, let's make unstable really unstable first by
> switching to gcc-3.2 as the default compiler (coming soon :-)
eheh. given that sarge won't be stable for another 12 months
(optimistically) 2.3 will have plenty of time to stabilize.
--
Federico Di Gregorio
Debian GNU/Linux Developer & Italian Press Contact fog@debian.org
INIT.D Developer fog@initd.org
Don't dream it. Be it. -- Dr. Frank'n'further
Attachment:
signature.asc
Description: PGP signature