| 1 |
Hum, maybe my little english is not good to explain my thoughts..... |
| 2 |
|
| 3 |
I already have a /usr/local/portage overlay bigger than 500Kb. |
| 4 |
|
| 5 |
What I was asking is if it's a normal behaviour that emerge "stops" for |
| 6 |
unstable branch users. |
| 7 |
I asked myself this after looking some ebuilds that have more than 4 |
| 8 |
versions in portage but |
| 9 |
still none of these (neither unstable or masked) works with gcc-4.1.x |
| 10 |
(for example fox, 11 different versions in portage and the gcc-4.1.x |
| 11 |
ebuild (stabled upstream) |
| 12 |
still floating in bugreport #132407 of 5-apr-2006 and bug #128917 of |
| 13 |
5-may-2006 , |
| 14 |
but fox is just an example, and there could be causes I don't know.......) |
| 15 |
|
| 16 |
No meant to harm anyone, sorry if you get mad, still completely my |
| 17 |
personal opinion and |
| 18 |
nothing more. |
| 19 |
|
| 20 |
mattepiu |
| 21 |
|
| 22 |
|
| 23 |
|
| 24 |
|
| 25 |
Alec Warner wrote: |
| 26 |
> Matteo Azzali wrote: |
| 27 |
>> This is just a mine question, but it seems that since gcc-4.1 got it's |
| 28 |
>> way into portage (~branch) things are getting slower. |
| 29 |
>> |
| 30 |
>> Lots of the bugs blocking bug #117482 - |
| 31 |
>> http://bugs.gentoo.org/show_bug.cgi?id=117482 - have a patch in the |
| 32 |
>> report |
| 33 |
>> or an ebuild for revision bump, tested working. |
| 34 |
>> They just don't get committed (or, sometimes, closed). |
| 35 |
>> |
| 36 |
>> IMHO these bugs should get some kind of "priority", cause actually any |
| 37 |
>> unstable system having one of these "blocking ebuilds" |
| 38 |
>> in world tree will have issue emerging,for sure. |
| 39 |
>> ( for who didn't noticed: gcc-4.1 is actually in portage testing , no |
| 40 |
>> more unmasked). |
| 41 |
> |
| 42 |
> Sometimes people get busy, I know I haven't looked at my bugs all |
| 43 |
> week, been busy at work 12 hours a day. As such if it's a big problem |
| 44 |
> you can always gcc-config <some-other-compiler-version> and then |
| 45 |
> compile any problem packages. I know that breaks the whole 'my whole |
| 46 |
> system is compiled w/gcc-4.1' deal, but if it's that big of a blocker, |
| 47 |
> take action. Or hell, patch the ebuild yourself. |
| 48 |
> |
| 49 |
> I think this distro was (or is?) about giving users the ability to do |
| 50 |
> what they needed. If something is masked, you can unmask it, if it's |
| 51 |
> not keyworded you can keyword it, if it's not patched, you can patch it |
| 52 |
> |
| 53 |
>> |
| 54 |
>> thanks for your time and for listening my 2 cents. |
| 55 |
>> |
| 56 |
>> mattepiu |
| 57 |
> |
| 58 |
|
| 59 |
-- |
| 60 |
gentoo-dev@g.o mailing list |
Archives