| 1 |
On Wed, Dec 28, 2011 at 05:47:18PM +0000, Duncan wrote: |
| 2 |
> IIRC this (and /etc/portage/patches) was originally deliberately kept an |
| 3 |
> "undocumented feature", to avoid trouble with missing info in bug |
| 4 |
> reports, since emerge info didn't report package specific information. |
| 5 |
|
| 6 |
This "/etc/portage/patches" thingie is something that the ebuilds must |
| 7 |
support themselves afaik (call epatch_user), although I can imagine a way to |
| 8 |
have it triggered for all systems by fiddling with /etc/portage/env too ;-) |
| 9 |
|
| 10 |
> Now that portage has emerge --info <pkg> and it's what's requested in the |
| 11 |
> usual output when a build aborts (tho AFAIK bugzilla still mentions |
| 12 |
> emerge info output only), and the logs themselves are rather better at |
| 13 |
> reporting user patches (for the patches subdir), that's not so much of a |
| 14 |
> problem, and the portage documentation itself mentions both usages of the |
| 15 |
> env subdir (tho not the patches subdir since that's still ebuild |
| 16 |
> activated). |
| 17 |
|
| 18 |
We might want to catch some bugzie admins then and suggest to update their |
| 19 |
page ;-) |
| 20 |
|
| 21 |
Wkr, |
| 22 |
Sven Vermeulen |
Archives