Skip Menu |
 

This queue is for tickets about the Dist-Zilla-Plugin-ReportVersions-Tiny CPAN distribution.

Maintainer(s)' notes

This module is deprecated!

This distribution has reached end-of-life now that better alternatives exist.

The recommended alternative is Dist::Zilla::Plugin::Test::ReportPrereqs.

Report information
The Basics
Id: 83266
Status: open
Priority: 0/
Queue: Dist-Zilla-Plugin-ReportVersions-Tiny

People
Owner: Nobody in particular
Requestors: dagolden [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: Suggest Dist::Zilla::Plugin::Test::ReportPrereqs for dynamic prereqs
Download (untitled) / with headers
text/plain 215b
Might be worth mentioning that Test::ReportPrereqs will pick up dynamic prereqs from MYMETA.json if CPAN::Meta is available, so is a good step-up if the static limitation of ReportVersions::Tiny is a problem. David
Download (untitled) / with headers
text/plain 381b
Le 2013-02-11 17:23:25, DAGOLDEN a écrit : Show quoted text
> Might be worth mentioning that Test::ReportPrereqs will pick up dynamic > prereqs from MYMETA.json if CPAN::Meta is available, so is a good > step-up if the static limitation of ReportVersions::Tiny is a problem. > > David
Added to SEE ALSO in the repo. Not yet released. Thanks. -- Olivier Mengué - http://perlresume.org/DOLMEN
Download (untitled) / with headers
text/plain 846b
On 2013-06-17 15:32:35, DOLMEN wrote: Show quoted text
> Le 2013-02-11 17:23:25, DAGOLDEN a écrit :
> > Might be worth mentioning that Test::ReportPrereqs will pick up dynamic > > prereqs from MYMETA.json if CPAN::Meta is available, so is a good > > step-up if the static limitation of ReportVersions::Tiny is a problem. > > > > David
> > > Added to SEE ALSO in the repo. Not yet released. > Thanks.
Would it be useful for the plugin to check dynamic_config in metadata, and issue a more strong warning at build time if it is set? such as a warning, rather than a simple informational message: "Warning: this distribution has dynamic_config=>1 - we may not be able to properly report on all actual prereqs." That would be a good clue for the developer that what's generated in this .t file may not be accurate, and they should swap out the implementation.
On 2013-06-23 09:27:13, ETHER wrote: Show quoted text
> On 2013-06-17 15:32:35, DOLMEN wrote:
> > Le 2013-02-11 17:23:25, DAGOLDEN a écrit :
> > > Might be worth mentioning that Test::ReportPrereqs will pick up
> dynamic
> > > prereqs from MYMETA.json if CPAN::Meta is available, so is a good > > > step-up if the static limitation of ReportVersions::Tiny is a
> problem.
> > > > > > David
> > > > > > Added to SEE ALSO in the repo. Not yet released. > > Thanks.
> > Would it be useful for the plugin to check dynamic_config in metadata, > and issue a more strong warning at build time if it is set? such > as a warning, rather than a simple informational message: "Warning: > this distribution has dynamic_config=>1 - we may not be able to > properly report on all actual prereqs." > > That would be a good clue for the developer that what's generated in > this .t file may not be accurate, and they should swap out the > implementation.
Implemented, in https://github.com/dolmen/p5-Dist-Zilla-Plugin-ReportVersions-Tiny/pull/7
Download (untitled) / with headers
text/plain 1.4k
Le 2013-06-23 18:27:13, ETHER a écrit : Show quoted text
> Would it be useful for the plugin to check dynamic_config in metadata, > and issue a more strong warning at build time if it is set? such > as a warning, rather than a simple informational message: "Warning: > this distribution has dynamic_config=>1 - we may not be able to > properly report on all actual prereqs."
No, I don't want to harrass developers with false positive. The dynamic config is not always about dynamic dependencies. And for the case of dynamic dependencies the developer can have them reported by ReportVersions::Tiny by listing them explicitely with the 'include' config option. If a module is neither listed in prereqs or as an 'include' I think that I can safely assume that the developer is not interested in the reporting of its version. Show quoted text
> That would be a good clue for the developer that what's generated in > this .t file may not be accurate
I expect the developer to check the output of its testsuite before a release. Show quoted text
> and they should swap out the > implementation.
Of course harassing the users of this module with false positive warnings is a good way to make them not use it anymore. So I will not merge the second commit of your PR. Karen, to extend my knowledge of the dynamic_config use case I'm interested in CPAN distributions you may have seen in the wild that use ReportVersions::Tiny with dynamic_config. Do you have some pointers? -- Olivier Mengué - http://perlresume.org/DOLMEN
oops, I reopened to mark it 'stalled', but I don't have the permissions to do that. sorry!
Download (untitled) / with headers
text/plain 361b
Le 2013-02-11 17:23:25, DAGOLDEN a écrit : Show quoted text
> Might be worth mentioning that Test::ReportPrereqs will pick up dynamic > prereqs from MYMETA.json if CPAN::Meta is available, so is a good > step-up if the static limitation of ReportVersions::Tiny is a problem.
Documented in the CAVEATS section added in 1.09. -- Olivier Mengué - http://perlresume.org/DOLMEN
Test::ReportPrereqs is now so mature that I will just mak ReportVersions::Tiny as deprecated and recommend Test::ReportPreqs for all uses.

-- 
Olivier Mengué - http://perlresume.org/DOLMEN - https://gratipay.com/dolmen/


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.