Miguel Filipe wrote:
> I've been trying to emerge gcc 4.0.2-r2, messing with
> /etc/portage/package.unmask & /etc/portage/package.keywords
> without success..
> the portage man page says that if a package has -* is know to be broken
> on all arches otherwise mentioned.
> So is 4.0.1, 4.0.0, 4.1-snapshot..
> I would expect it to be at least marked unstable "~amd64 .."
I hope you really know what you are doing (or trying to do). gcc-4.0 isn't
broken, but it is hard-masked because there are *major* changes, meaning you
should rebuild your whole system with it once you upgraded. That's why it is not
yet ~amd64 and we want to give it a long testing period. Another issue is that
gcc-4.0 is even stricter than 3.4, meaning lots of packages won't build anymore.
That's why we marked it -*, because we don't want to disappoint normal users who
aren't familiar with writing patches. And those who are, are clever enough to
unmask a hard masked package, it's not that hard after all.
> gentoo seems to have major problems in keeping up with the public
> releases.. its starting to look like debian stable....
Is this a 'i want to help'?
> also.. I don't see the point in having 3 types of tags: stable,
> unstable, broken.. maybe the same point of (stable, testing, unstable..
> ala debian)
You're mixing up quite unrelated things. -* is generally used for packages that
are only available for one or two arch (typical example: binary packages). When
it means 'broken', then it is only in the tree because it makes it easier for
devs to share ebuilds which they (and of course the 'advanced' users) can test.
> Nevermind, basically, I'm using gentoo since 1.0rc6 and starting to be
> disapointed by the slowness of having fresh software available..
If you feel more adventurous, use package.(unmask|keywords). It's a wonderful
tool to let the user decide himself what is stable enough for him.
> gnome 2.12 came out 7 of september, maybe when gnome 2.14 is out I can
> find it keyworded "amd64"..
Again, package.keywords if you agree. Since 1.0rc6, Gentoo has changed a lot.
We've got a huge user base, and we really don't feel like getting the same bug
reported 10 times just because we marked some untested piece of software stable.
It won't make most users very happy either, especially those who want a system
that 'just works'.
> In conclusion, package mantainance needs a new organizational way to scale..
> Or should I simply move to ~amd64, just like any debian user sets its
> system to testing without thinking twice, just after the install.
Moving to ~amd64 could be the right thing for you. But if you're running ~amd64
and get tons of bugs, don't bitch. Personally, I think everybody who runs ~amd64
should be filing bugs whenever he hits one. If you don't want to do that, keep
your system stable.
Gentoo/AMD64 Operational Co-Lead
email@example.com mailing list