| 1 |
On 17:35 Wed 01 Dec , Diego Elio Pettenò wrote: |
| 2 |
> > Comments inside are better suited for this task - you see/update notes |
| 3 |
> > as you edit ebuild. |
| 4 |
> > |
| 5 |
> How many ATs/arch maintainers will look _within_ the ebuild when testing |
| 6 |
> an ebuild for stable? |
| 7 |
|
| 8 |
I agree, comments within the ebuild are practically invisible to |
| 9 |
archteams (at least to me for x86). But also running repoman is usually |
| 10 |
the final step, right before committing. The place for comments that |
| 11 |
need to be considered during archtesting would be right in the stable |
| 12 |
request bug. This is where I usually start. |
| 13 |
|
| 14 |
If I do normal build tests first and then find they have been in vain |
| 15 |
when running repoman, then I wasted cycles for the build tests. I'm |
| 16 |
unsure if this would apply to your original example, though. |
| 17 |
|
| 18 |
Cheers, |
| 19 |
Thomas |
| 20 |
|
| 21 |
|
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Thomas Kahle |
| 26 |
http://dev.gentoo.org/~tomka/ |
Archives