Re: attempt at using most perl modules
On Sat, Apr 21, 2018 at 04:58:22PM -0700, Don Armstrong wrote:
> This is actually expected; Apache::Gallery is a mod perl module, and
> won't work properly outside of it. [This failure is because it's trying
> to detect mod_perl vs mod_perl2 and MOD_PERL_API_VERSION isn't set;
> Debian just depends on mod_perl2 since we don't ship mod_perl 1.]
Indeed, there are many false positives in the list. I found 25 failures
that seem actual bugs to me (mostly missing dependencies), and I'm filing
them with the usertag debian-perl@lists.debian.org / use-failures.
https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=use-failure&user=debian-perl%40lists.debian.org
The rest are things working as documented/intended, with the failures
due to things like:
* needs a $DISPLAY
* not meant to be used directly
* meant to be used under mod_perl2 or nginx
* needs 'use base "something' first
* wants an explicit import list
* should be used from a test script
* wants to write to cwd or $HOME
I'm not aware of a strict requirement for Perl modules in general to
survive a simple 'use Module' setting (although most certainly do),
and I don't think we should try to mandate one in Debian. If upstream
has designed the module for a different use case and documented that,
I think it's just fine.
FWIW our standard autopkgtest-pkg-perl framework includes a test for
exactly this, but can be overridden on by-package basis in cases like
the above. The coverage isn't 100% yet but I think we've found quite a
few similar bugs with it.
https://perl-team.pages.debian.net/autopkgtest.html#use.t
--
Niko Tyni ntyni@debian.org
Reply to: