First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 250212
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Portage team <dev-portage@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Mike Auty <ikelos@gentoo.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
repoman-emake-warning.patch Patch for trunk that adds "upstream.workaround" and associated help text patch Mike Auty 2008-12-07 22:10 0000 2.29 KB Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 250212 depends on: Show dependency tree
Bug 250212 blocks: 210077 216231
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2008-12-07 22:07 0000 
It's really confusing to be receive an error "ebuild.minorsyn" simply because
an ebuild used "emake -j1".  Looking at the repoman help, an ebuild.minorsyn
is:
"This ebuild has a minor syntax error that contravenes gentoo coding style".

emake -j1 is neither a syntax error, nor does it contravene gentoo coding
style.  In fact, it's recommended (see bug 250141).

As such, I'd suggest a new category "upstream.workaround" with a better
description of the problem, suggesting that the text used is in fact a
workaround for an upstream bug, and that a bug should be filed upstream and
tracked in gentoo's bug tracker.

------- Comment #1 From Mike Auty 2008-12-07 22:10:17 0000 ------- 
Created an attachment (id=174604) [edit]
Patch for trunk that adds "upstream.workaround" and associated help text

This is the first patch I've made for portage, as such I dunno if I managed to
make changes in all the appropriate places.  Do feel free to reword it if the
wording is awkward or unclear.  This should apply to portage trunk (r12174). 
Please let me know if there are any issues with it, or any mistakes, etc. 
Thanks...  5:)

------- Comment #2 From Zac Medico 2008-12-08 03:26:31 0000 ------- 
Thanks, your patch is in svn r12179.

------- Comment #3 From Zac Medico 2008-12-13 00:31:08 0000 ------- 
This is in 2.1.6.1.
First Last Prev Next    No search results available      Search page      Enter new bug