2009-09-20 16:53:37 Jesús Guerrero napisał(a): > On Sun, 20 Sep 2009 00:41:32 +0200, Dawid Węgliński <c...@gentoo.org> > wrote: > > On Sunday 20 of September 2009 00:32:28 Dale wrote: > >> > > >> > ~arch is for testing ebuilds, not the upstream package > >> > >> So it would be OK to mark something "stable" even tho portage itself > >> doesn't work with it? Sorry, this makes no sense to me. I run stable > >> for the most part and having a package that portage depends on that is > >> not stable just sounds a little like putting the cart before the horse. > >> > >> See some of the other replies as to why this is a not so good idea. > >> > >> Dale > >> > >> :-) :-) > > > > You mix it up. Portage works with python 3.1. If an user switches to > > python > > 3.1 as the main interpreter, it's possible that his own scripts won't > > work. > > Yes? > > # eselect python set 2 > # emerge -s foo > File "/usr/bin/emerge", line 41 > except PermissionDenied, e: > ^ > SyntaxError: invalid syntax > > > Ummm, yes, it works *beautifully*, you see. Nothing else to add.
I have fixed it today :) . http://sources.gentoo.org/viewcvs.py/portage?rev=14289&view=rev > > Marking it stable sometine in november give's some time to ebuilds > > maintainers to fix their python based apps just like it's done with gcc > > stabilization. > > That's not the usual case. In Gentoo we have a serious policy of not > marking as stable things until it has passed one month without any serious > bug report about it. There wasn't any serious bug report about Python 3.1. IIRC the only problem was a (already fixed) build failure caused by non-UTF-8 characters in header of Berkeley DB. Stabilization of Python 3.1.1-r1 is planned over 1 month after its addition to the tree and about 3 months after addition of 3.1 slot to the tree. -- Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
