Hi Petr
On 23/11/15 22:56, Petr Pisar via RT wrote:
Show quoted text> Mon Nov 23 06:56:54 2015: Request 109480 was acted upon.
> Transaction: Ticket created by ppisar
> Queue: Module-Metadata-Changes
> Subject: Dependency on non-existing HTML::Entities::Interpolate 1.06
> Broken in: 2.06
> Severity: (no value)
> Owner: Nobody
> Requestors: ppisar@redhat.com
> Status: new
> Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=109480 >
>
>
> The Module-Metadata-Changes-2.06 run-requires HTML::Entities::Interpolate 1.06 version but the latest release is 1.05.
Thanx for this email. It's of great significance for me.
I had forgotten to upload V 1.06 to CPAN, so my apologies for that.
I have just uploaded V 1.07, with no code changes, but a new
scripts/synopsis.pl and a meaningful test using this program.
Show quoted text> Actually a lot of dependency declarations changed version. Is that necessary?
This is an awkward question! I had installed V 1.06 locally, so when I
ran mversion (from Module::Version), I thought V 1.06 had been released.
Similarly, for the other modules, I (usually) check their versions I've
installed and keep Makefile.PL up-to-date.
I do realize this inconveniences some users, and that is regrettable.
But I can see no perfect answer to tracking updates in other modules and
releasing modules with a stable set of pre-reqs.
Obviously if I don't rely on new features of a module, I don't need to
update the pre-reqs. But then I worry about bug fixes in those updates.
V 1.07's new test uses Capture::Tiny and File::Slurper for the 1st time,
but the versions of the other module (in Makefile.PL) have not changed.
And yes, adding 2 new dependencies will worry some users, but in my
defence I'll say the new test - while minor - is immeasurably better
that the old t/load.t, and is part of my on-going plan to make all
modules' tests better.
--
Ron Savage - savage.net.au
