#6076 closed enhancement (fixed)
Test-Command-0.11
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | 7.7 |
| Component: | BOOK | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description
feh requires this if its test suite is to run.
I am ambivalent about this (I do not find feh useful, for me ImageMagick's display is more convenient), but I'm willing to add it if nobody objects).
I might have created the thin end of the wedge by recommending the test perl module deps for biber, and therefore adding them, but in that case the latest of biber broke at runtime and its make test showed that.
If no objections, I ill do this with the other perl module tickets I've got _after_ I've completed my fresh builds.
Change History (9)
comment:1 by , 9 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 9 years ago
comment:3 by , 9 years ago
No, it is perl module, that is the reason I suggested it. But if you still think it is not worth it and Ken agrees, it is OK with me.
comment:4 by , 9 years ago
Sorry. It wasn't apparent that it was a Perl module. Adding that is OK. To be honest, I always use the alternate cpan instructions because it's still from source and a lot faster.
follow-up: 8 comment:5 by , 9 years ago
This one will take me a little longer to test (it's a server package, I use it for SpamAssassin, will be building a VM to test my server stuff). But I took a look to see what in the book uses this, in case that was a quicker way to test, and only Bind optionally uses this, so we already have a precedent for listing optional dependencies which are perl modules.
follow-up: 9 comment:8 by , 9 years ago
Replying to ken@…:
This one will take me a little longer to test (it's a server package, I use it for SpamAssassin, will be building a VM to test my server stuff). But I took a look to see what in the book uses this, in case that was a quicker way to test, and only Bind optionally uses this, so we already have a precedent for listing optional dependencies which are perl modules.
Sorry, that was intended for a different ticket.
Is this a complicated build? If it's only CMMI, is would prefer just leaving it as an external dependency with a note that it is required for testing.
The point is that I would prefer to avoid obscure, one time packages in the book. It just makes maintenance harder and few people will use it.