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