Summary: | app-portage/eclass-manpages - producing bogus warnings and parsing eclasses it shouldn't | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jakub Moc (RETIRED) <jakub> |
Component: | New packages | Assignee: | SpanKY <vapier> |
Status: | VERIFIED INVALID | ||
Severity: | normal | CC: | java |
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jakub Moc (RETIRED)
2007-09-01 17:48:56 UTC
there are no bogus warnings ... the awk tries to extract the default value to display it in the manpage but the way you've written the eclass prevents that from happeneing OMG, are you joking or what? *What's* preventing the eclass from being parsed? What kind of default value? Could you finally answer that simple question? And why is it parsing eclasses it should NOT parse at all since there's no @ECLASS at all in the first place? comment blocks are supposed to appear before the default variable setting so that the default value can be extracted and displayed if it doesnt, you get a warning, and the manpage does not display the default value (In reply to comment #3) > comment blocks are supposed to appear before the default variable setting so > that the default value can be extracted and displayed > > if it doesnt, you get a warning, and the manpage does not display the default > value Please, don't try to do impossible things in the script. If there's a default value, it's up to the eclass to document if desired, instead of performing broken black magic somehow via the awk script. Now, what's the thing with trying to parse java-ant-2.eclass, java-utils-2.eclass, java-vm-2.eclass, webapp.eclass? This script's acting like a bull seeing a red cloth whenever it hits @ character. if you dont want your var documented, then ignore the warning (In reply to comment #5) > if you dont want your var documented, then ignore the warning Apparently asking two questions at a time doesn't work... let's try again then: <snip> What's the thing with trying to parse java-ant-2.eclass, java-utils-2.eclass, java-vm-2.eclass, webapp.eclass? This script's acting like a bull seeing a red cloth whenever it hits @ character. </snip> The script fails to ignore eclasses that have no @ECLASS tag there, spewing the users with hundreds of irrelevant warnings. Can we get this fixed please? fix the eclass (In reply to comment #7) > fix the eclass Yeah, clearly asking for the script to behave consistently and ignore eclasses unless it contains "@ECLASS: " (and exactly that, with exactly that case and nothing else containing any substrings of that) is mission impossible. Even if the java eclasses get "fixed", the script will still be broken because webapp.eclass doesn't contain any @ECLASS variant at all, yet it causes the same issue, because it contains other things with @ which trigger the awk script misbehaviour. I might suggest that people should think about design before writing up something, as @ apparently plain sucks as a tag (a quick grep through the existing eclasses would have shown this at the very beginning) - but at this point I plain don't care enough any more, wasted enough time on this broken script that's spamming users with junk. |