1 |
Greetings - |
2 |
|
3 |
Occasionally, I've contacted developers about repoman issues with |
4 |
ebuilds when things are broken in portage. I generally run repoman |
5 |
on the entire portage tree - a process that takes quite some time - |
6 |
since not everyone wants to do this. |
7 |
|
8 |
Frequently, the only new changes in the repoman report are the addition |
9 |
of some warnings regarding whitespace - either Leading or Trailing. |
10 |
For these warnings, I generally just fix the ebuilds myself since the |
11 |
change is obvious and contacting developers about whitespace warnings |
12 |
is pretty silly. If you find this happening to your favorite ebuild |
13 |
please just take this as a gentle nudge to not ignore the repoman |
14 |
warnings when you commit and move on with your life. |
15 |
|
16 |
My expectation is that every commit to the portage tree is as |
17 |
"repoman free" as possible. At one point, the repoman report was |
18 |
over 20k lines. Let's not go there again. |
19 |
|
20 |
Thanks, |
21 |
|
22 |
Michael Sterrett |
23 |
-Mr. Bones.- |
24 |
mr_bones_@g.o |
25 |
|
26 |
|
27 |
-- |
28 |
gentoo-dev@g.o mailing list |