| 1 |
Ehrm, I'm already becomed developer (some days) *, |
| 2 |
I'm already the author of lots of patches/comment in those reports, |
| 3 |
and as you pointed out I must follow rules and can't "jump" maintainers |
| 4 |
(who surely have better understanding of the issue involved than me). |
| 5 |
|
| 6 |
That's the cause of the question,my (little?) brain asked me |
| 7 |
"Why there are so much version of a package in portage, and why |
| 8 |
following bugs for |
| 9 |
version that aren't the latest stable and the latest unstable (for any |
| 10 |
arch) instead of |
| 11 |
ensuring that those 2/3 versions work fine?" , I mean, because in some |
| 12 |
cases a revision |
| 13 |
bump is necessary to let unstable work fine, (and these will be |
| 14 |
necessary however when |
| 15 |
gcc-4.x will become stable) why delaying trying to fix bugs specific of |
| 16 |
older versions, |
| 17 |
probably resolved upstream with new ones? |
| 18 |
|
| 19 |
(I know, my brain is nasty and doesn't works as others may expect). |
| 20 |
|
| 21 |
|
| 22 |
Other than this, 23MB of overlay? But you "clean" it or you keep stored |
| 23 |
every line |
| 24 |
of code you wrote? |
| 25 |
If you regularly clean your overlay (keeping no more than 2-3 ebuilds |
| 26 |
for package), |
| 27 |
then it's really huge and impressive! |
| 28 |
|
| 29 |
mattepiu@g.o |
| 30 |
|
| 31 |
* (I'm not sending mails through gentoo.org account cause |
| 32 |
http://www.gentoo.org/proj/en/infrastructure/dev-email.xml |
| 33 |
asks me to not use it to send mails "unless absolutely necessary." , and |
| 34 |
I have others mean of sending emails....) |
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
Chris Bainbridge wrote: |
| 39 |
> On 08/06/06, Matteo Azzali <matte.az@××××××.it> wrote: |
| 40 |
>> Hum, maybe my little english is not good to explain my thoughts..... |
| 41 |
>> |
| 42 |
>> I already have a /usr/local/portage overlay bigger than 500Kb. |
| 43 |
> |
| 44 |
> I can beat that, try 23MB :-/ |
| 45 |
> |
| 46 |
> Anyway, back to your point - yes, there are lots of bugs with patches |
| 47 |
> attached that aren't being added to the main tree. And there are lots |
| 48 |
> of bugs where the ebuild or fix is ending up in an overlay rather than |
| 49 |
> the main tree. It's getting complicated to keep track - all I can |
| 50 |
> really advise is that if you'd like to see fixes and ebuilds being |
| 51 |
> added to the main tree, then become a developer and start doing it |
| 52 |
> (although it is complex for something like gcc compile fixes which are |
| 53 |
> spread across packages owned by multiple developers who will get upset |
| 54 |
> if you touch their package). |
| 55 |
|
| 56 |
-- |
| 57 |
gentoo-dev@g.o mailing list |
Archives