Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
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.
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.
So marking python 3.1 stable and telling users "port your own apps/scripts to
current python" sounds good to me.
|
|
