r76960 - /trunk/dh-make-perl/TODO

[dmn at users.alioth.debian.org]

Author: dmn
Date: Sat Jul  2 12:50:20 2011
New Revision: 76960

URL: http://svn.debian.org/wsvn/pkg-perl/?sc=1&rev=76960
Log:
TODO -= possible use of system-wide DhMakePerl/dh-make-perl in tests

dh-make-perl is run from a location relative to the test itself, so it is not
the system-wide.
as for the modules, the tests are run with PERL5LIB set to the working copy (or
some staging directory Module::Build have set up) and PERL5LIB variable is
exported via the system() call.
as a confirmation, running the tests locally (not in a chroot) after changing
the default debhelper level to 8 in DhMakePerl::Config (and in
t/dists/*/wanted-debian*/{control,compat}) shows no problems even if the
system-wide dh-make-perl still defaults to dh7.

Modified:
    trunk/dh-make-perl/TODO

Modified: trunk/dh-make-perl/TODO
URL: http://svn.debian.org/wsvn/pkg-perl/trunk/dh-make-perl/TODO?rev=76960&op=diff
==============================================================================
--- trunk/dh-make-perl/TODO (original)
+++ trunk/dh-make-perl/TODO Sat Jul  2 12:50:20 2011
@@ -27,11 +27,6 @@
 * different rules files: do we still need share/rules.*?
   and: is the POD still correct about rules.MakeMaker and rules.Module-Build?
   we depend on debhelper >= 7
-* I noticed a problem with the dists.t test script. It essentially does
-  a system("dh-make-perl"). This causes two problems. Firstly it is a pain to
-  debug if something goes wrong. More seriously there is a tendency to pick
-  up the wrong DhMakePerl library invalidating the tests. Really the DhMakePerl
-  API should be used directly. ~periapt
 * Really minor issue. The AptContents.t test can be thrown off if the contents
   directory has stuff lying around from a failed run. ~periapt
 * Add a switch for "app" (foo-bar) vs. "lib" (libfoo-bar-perl) packages?