Bug 209665 - app-portage/eclass-manpages states @DESCRIPTION as optional but doesn't create manpage if @DESCRIPTION is missing
|
Bug#:
209665
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: vapier@gentoo.org
|
Reported By: bugs@rennings.net
|
|
Component: Unspecified
|
|
|
URL:
|
|
Summary: app-portage/eclass-manpages states @DESCRIPTION as optional but doesn't create manpage if @DESCRIPTION is missing
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2008-02-11 15:48 0000
|
In eclass-to-manpage.awk it's stated:
# @DESCRIPTION:
# <optional; long description>
But w/ a missing @DESCRIPTION it skips the creation of that manpage:
/usr/portage/eclass/python.eclass:11:error: python.eclass: no @DESCRIPTION
found
Reproducible: Always
python.eclass is not eclass-manpages compatible at all. If you are annoyed by
the useless noise, see Bug 190981, I gave up.
The noise doesn't matter to me (in that case). It's just that I'm writing
patches for eclasses and I stumbled upon the "problem" that @DESCRIPTION in
@ECLASS-context seems not to be optional. The python.eclass was just the one I
wrote the patch for as I noticed the problem.
(In reply to comment #2)
> The python.eclass was just the one I wrote the patch for as I noticed the problem.
Meh... sorry; that was indeed a bad example. :)