> On 6 Sep 2001, Mikael Hedin wrote:
>
> > What about doing as gcc? Produce python-1.5, python-2.1 and so on
> > forever. And then have a package python that just drags in the
> > official version, and links /usr/bin/python. If we nuke python-base,
> > all old modules get upgradrd I think. (Si
On 6 Sep 2001, Mikael Hedin wrote:
> What about doing as gcc? Produce python-1.5, python-2.1 and so on
> forever. And then have a package python that just drags in the
> official version, and links /usr/bin/python. If we nuke python-base,
> all old modules get upgradrd I think. (Similar for py
What about doing as gcc? Produce python-1.5, python-2.1 and so on
forever. And then have a package python that just drags in the
official version, and links /usr/bin/python. If we nuke python-base,
all old modules get upgradrd I think. (Similar for python-foo etc.)
The only problem I see is th
3 matches
Mail list logo
