[Pkg-sql-ledger-discussion] Problem pod NAME entries in Perl files

Robert James Clay jame at rocasa.us
Mon Jan 9 16:32:36 UTC 2012


On Mon, 2012-01-09 at 03:06 -0500, Raphael Hertzog wrote:
> On Sun, 08 Jan 2012, Robert James Clay wrote:
> > > ....
> > > +# Override instances of the manpage-has-bad-whatis-entry Lintian warning,
> > > +# which results from issues with the pod NAME entries in the cooresponding
> > > +# Perl source files.
> > > +ledgersmb: manpage-has-bad-whatis-entry
> > 
> >    The reason I'm putting that in is that I've found some 50 Perl source
> > files that have various types of issues with the pod NAME entries in the
> > files, which end up causing the above Lintian warnings after the man
> > pages are created from them.  ....

> I don't think this justifies an override.

   I consider this as only a temporary measure.


>  Those are issues that should be fixed and not hidden.

   They will be fixed and I don't consider them "hidden"; rather,
they're simply not displayed in detail by default. And I don't consider
50 warnings of the same type that I already know about, have already
investigated and have the details for, and that only indirectly points
to where the problems are in any case (in that the error only shows up
in the man page because of the problem in the source file), to be
particularly useful each time a lintian check runs. 

   Having said that, I'm already checking with upstream about them. In
part to see if I can get an idea of how long it will take to get them
fixed there (after all, these might be the type of thing they'd work on
only if they already needed to work on the file); and if they want to
track them by the individual files or by the type of problem.  Once I
have an idea of that, I'll be able to proceed with the patches as
necessary.

   Btw;  if there is a way to set such overrides temporarily, so it's
easier to check for possible issues I don't already know about without
having to make the change in the package build itself, I'd like to know.
(Using lintian profiles, perhaps?)


> It's not a big deal if they are not fixed immediately and if they keep
> showing up for some time. OTOH, they are all really easy to fix by
> enhancing the POD in the corresponding source files.

   Individually they're easy to fix but there are 50 of them (that I
know about) and some of them are easier to fix than others...<g>





Jame





More information about the Pkg-sql-ledger-discussion mailing list