Bug 1385280

BTW, on my system there are 386 directories /usr/share/doc/perl-*, and only 26 /usr/share/doc/perl-*/t/ directories:

$ ls -1 -d perl-*/t 
perl-App-Cmd/t
perl-B-Hooks-EndOfScope/t
perl-B-Hooks-OP-Check/t
perl-Business-ISBN-Data/t
perl-Class-Method-Modifiers/t
perl-common-sense/t
perl-CPAN-Meta/t
perl-Data-OptList/t
perl-Devel-GlobalDestruction/t
perl-Devel-LexAlias/t
perl-Devel-Size/t
perl-HTML-Tidy/t
perl-Moose/t
perl-MooseX-ConfigFromFile/t
perl-MooseX-Getopt/t
perl-MooseX-Role-Parameterized/t
perl-MooseX-StrictConstructor/t
perl-MooseX-Types-Path-Class/t
perl-MooseX-Types/t
perl-MRO-Compat/t
perl-namespace-clean/t
perl-Scope-Guard/t
perl-Sub-Exporter/t
perl-Sub-Identify/t
perl-Test-Simple/t
perl-Try-Tiny/t

perl-App-Cmd-0.330-3.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-49887ecd61

perl-App-Cmd-0.331-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-c5a776d731

perl-App-Cmd-0.330-3.fc24 works for me. What about other 25 packages?

(In reply to Van de Bugger from comment #4)
>
> What about other 25 packages?

You'll have to file bugs.

> You'll have to file bugs.

25 bugs? It's ridiculous.

It's ridiculous generalizing all the tests are not worth of documentation. Have studied each of the packages? Sometimes the tests are the only available useful documentation. Each package must be considered specially, therefore a bug report for each of them.

Moreover from logistic point of view, not all of them are maintained by Emanuel. Their maintainers are not aware of your concerns. The right way in Fedora is to file a bug report for each of them.

(In reply to Van de Bugger from comment #6)
> 
> 25 bugs? It's ridiculous.

Note that that's what on your system. I'm sure there are more packages affected.

I plan to evaluate the need to remove tests on a case by case basis. While perl-App-Cmd's documentation is good enough that it is not necessary to include  the tests as examples of use of the module, I can't guarantee that all modules 
are like this.

It would help if you explained why you feel this is a bug. Is there an inconvenience to having the t/ directory ship in the documentation? Do they take up too much disk space? Do they drag in otherwise-unneeded deps?

> It's ridiculous generalizing all the tests are not worth of documentation. 

They are tests, not examples.

> It would help if you explained why you feel this is a bug.

It is my feeling.

I already said that tests are part of Perl distribution. Perl distribution installer (either cpan, cpanp, or cpanm), unpacks distribution archive, builds the module (if there are parts written in C), run tests (optionally send reports), and installs the module to the system. Tests are *not* installed. They remain in the temporary directory, which is usually removed soon. (I have large local Perl library installed directly from CPAN, it contains ~1500 *.pm files and *no* *single* *.t file.)

RPM package contains prebuilt and "pretested" software. Packed software was built and tested when RPM itself was building. When RPM package is installing to the user system, it just copies files (no source compiling, no testing at all (akmods are exception)). If original Perl distribution does not install tests, why RPM does it?

> Sometimes the tests are the only available useful documentation. 

Anyway, it is not a reason for installing tests. End-users are not interested in tests at all. Developers may be interested, but… Did RPM packager take care about *test dependencies*? Tests may have specific requirements. For a Perl developer having local Perl library (of modules installed directly from CPAN) have many advantages over using RPMs.

> Each package must be considered specially…

Indeed, it would be much better to have a policy. 

Again: If original Perl distribution does not install tests, why RPM does it?

(In reply to Van de Bugger from comment #9)
> 
> They are tests, not examples.

In practice, they are sometimes the only examples of use of the module.

> If original Perl distribution does not install tests, why RPM does it?

For the same reason we convert files to UTF-8 or apply patches to better integrate the modules in the system: the benefits for our users outweigh
the costs.

> Anyway, it is not a reason for installing tests. End-users are not
> interested in tests at all. Developers may be interested, but… Did RPM
> packager take care about *test dependencies*?

We usually use the macro %{?perl_default_filter} in our spec files which
tells RPM not to use provides and requires from the documentation.

> Indeed, it would be much better to have a policy.

That sounds like a job for FESCo.

perl-App-Cmd-0.330-3.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.

perl-App-Cmd-0.331-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.