Matteo Azzali wrote:
This is just a mine question, but it seems that since gcc-4.1 got it's
way into portage (~branch) things are getting slower.
Lots of the bugs blocking bug #117482 -
http://bugs.gentoo.org/show_bug.cgi?id=117482 - have a patch in the report
or an ebuild for revision bump, tested working.
They just don't get committed (or, sometimes, closed).
IMHO these bugs should get some kind of "priority", cause actually any
unstable system having one of these "blocking ebuilds"
in world tree will have issue emerging,for sure.
( for who didn't noticed: gcc-4.1 is actually in portage testing , no
more unmasked).
Sometimes people get busy, I know I haven't looked at my bugs all week,
been busy at work 12 hours a day. As such if it's a big problem you can
always gcc-config <some-other-compiler-version> and then compile any
problem packages. I know that breaks the whole 'my whole system is
compiled w/gcc-4.1' deal, but if it's that big of a blocker, take
action. Or hell, patch the ebuild yourself.
I think this distro was (or is?) about giving users the ability to do
what they needed. If something is masked, you can unmask it, if it's
not keyworded you can keyword it, if it's not patched, you can patch it
thanks for your time and for listening my 2 cents.
mattepiu
--
gentoo-dev@gentoo.org mailing list
