1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
Source: libmodule-install-authorrequires-perl
Section: perl
Priority: optional
Build-Depends:
debhelper-compat (= 13),
libmodule-install-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: Jonas Smedegaard <dr@jones.dk>
Standards-Version: 4.7.2
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libmodule-install-authorrequires-perl.git
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libmodule-install-authorrequires-perl
Homepage: https://metacpan.org/release/Module-Install-AuthorRequires
Testsuite: autopkgtest-pkg-perl
Package: libmodule-install-authorrequires-perl
Architecture: all
Depends:
libmodule-install-perl,
${misc:Depends},
${perl:Depends}
Description: declare author-only dependencies
Modules often have optional requirements, for example dependencies that
are useful for (optional) tests, but not required for the module to
work properly.
.
Usually you want all developers of a project to have these optional
modules installed. However, simply telling everyone or printing
diagnostic messages if optional dependencies are missing often isn't
enough to make sure all authors have all optional modules installed.
.
Module::Install already has a way of detecting an author environment,
so an easy way to achieve the above would be something like:
.
if ($Module::Install::AUTHOR) {
requires 'Some::Module';
requires 'Another::Module' => '0.42';
}
.
Unfortunately, that'll also make the optional dependencies show up in
the distributions "META.yml" file, which is obviously wrong, as they
aren't actually hard requirements.
.
Working that around requires a considerable amount of non-trivial
Makefile.PL hackery, or simply using Module::Install::AuthorRequires's
"author_requires" command.
|
