Bug#608936: dh-make-perl: not to create ${PACKAGE}.docs for autocreated README

2011-07-21 Thread Damyan Ivanov
-=| Nicholas Bamber, Thu, Jan 06, 2011 at 09:27:12PM + |=- Actually you are proposing my first idea but I thought the create_readme parameter was more elegant. May be that is a Build.PL bias. for determining the main file,Makefile.PL has a VERSION_FROM parameter. Build.PL has a

Bug#608936: dh-make-perl: not to create ${PACKAGE}.docs for autocreated README

2011-01-06 Thread Damyan Ivanov
Agreed, the revival of useless README in $pkg.docs is really annoying. -=| Nicholas Bamber, Tue, Jan 04, 2011 at 06:53:30PM + |=- At least for Build.PL detecting autogenerated README should be easy enough. There is a a create_readme option which is an absolute give away. Is it possible

Bug#608936: dh-make-perl: not to create ${PACKAGE}.docs for autocreated README

2011-01-06 Thread Nicholas Bamber
Damyan, Actually you are proposing my first idea but I thought the create_readme parameter was more elegant. May be that is a Build.PL bias. for determining the main file,Makefile.PL has a VERSION_FROM parameter. Build.PL has a dist_version_from parameter. And obviously if you cannot

Bug#608936: dh-make-perl: not to create ${PACKAGE}.docs for autocreated README

2011-01-04 Thread Nicholas Bamber
Package: dh-make-perl Version: 0.71-1 Severity: wishlist Tags: upstream The README file is often autocreated and completely duplicates the man page. As such it is not installed. However dh-make-perl will always add README to the debian/$PACKAGE.docs file. This means that the packager has to