On Mon, Nov 29, 2010 at 04:47:36PM +0100, Arfrever Frehtes Taifersar Arahesis 
wrote:
> 2010-11-29 12:43 Sebastian Pipping <sp...@gentoo.org> napisał(a):
> > On 11/29/10 02:35, Arfrever Frehtes Taifersar Arahesis wrote:
> >> Sebastian Pipping recently removed automatic upgrade of active version of 
> >> Python, so
> >> python-2.7.1.ebuild does not upgrade active version of Python.
> >
> > The ebuilds you just added for 2.7.1 and 3.1.3 do contain
> > eselect_python_update() and calls to it.
> >
> > I suppose that happened by mistake and removed eselect_python_update()
> > on these ebuilds, too.  They are in CVS now, mirrors take extra time.
> 
> It wasn't any mistake. Please actually read that code:
> 
> eselect_python_update() {
>       if [[ -z "$(eselect python show --python${PV%%.*})" ]]; then
>               eselect python update --python${PV%%.*}
>       fi
> }
> 
> "${PV%%.*}" == "2"
> 'eselect python update --python2' would be called only if output of
> 'eselect python show --python2' was empty, which would occur when
> there was no active version of Python 2 set (no /usr/bin/python2
> symlink).
> 
> --
> Arfrever Frehtes Taifersar Arahesis

I updated two systems and they both switched to 2.7.1 automatically.

They were working fine with 2.6 before the update.
-- 
Alex Alexander | wired
+ Gentoo Linux Developer
++ www.linuxized.com

Attachment: pgpiaF7y7PtID.pgp
Description: PGP signature

Reply via email to