-=| Kevin Ryde, Sat, Apr 10, 2010 at 10:23:09AM +1000 |=-
> gregor herrmann <gre...@debian.org> writes:
> >
> > * dh-make-perl should handle this case a bit more gracefully (by not
> >   inserting blank lines in debian/control's Description).
> 
> Yep, don't generate an invalid file :-).  Doesn't have to look good for
> personal use of course, just work.

I agree. In fact the development version of dh-make-perl (in SVN) 
doesn't suffer from this problem. A nice side effect of refactoring 
description handling :)

However, I'd like to know what do you think is the best course of 
action when no long description (or an empty one) is found.

The current SVN code would leave the package with no long description 
at all:

--------------
...
Description: something
-----[EOF]----

For some reason, when adding this situation in the test suite, I made 
it to expect the following:

--------------
...
Description: something
 (no description was found)
 .
 This description was automagically extracted from the module by dh-make-perl.
-----[EOF]----

Both would trigger a lintian complaint (serious and normal, 
respectively).

Which one would you prefer?

Thank you for your input.

Attachment: signature.asc
Description: Digital signature

Reply via email to