Re^5: Deciding dependency versions

I hadn't encountered the idea of "rely on Makefile.PL" previously. As I said, "I didn't think that would be enough", but I didn't know for sure. The tests were as much for my benefit as yours. I was surprised that I only got a warning re Perl version.

I have the impression that you're in the process of providing other updates for your module. I'd be inclined to include "use VERSION;" with the next set of updates.

From v5.12 onwards, new versions have been released annually (mostly in May or June); in general, v5.x.y versions (where x is even and y > 0) have been compatible with 5.x.0, the few exceptions (just 3 or 4, I think) have only had minor incompatibilities. v5.10.1 was incompatible with v5.10.0 (from memory, mostly, or perhaps entirely, due to the '~~' operator). v5.8.0 to 5.8.9 were more like a series of completely new releases, which is why they're spread over a longer period than we're currently seeing — I recall working remotely a lot during that period and was bitten a few times with code that worked on the v5.8.x that I had installed at home, failing on the v5.8.x-1 that was installed at $work.

I suppose people will have their own views on where legacy ends and toolchain begins. I currently have to support v5.14 for $work; but that's planned to change to v5.26 in the not-too-distant future. I have seen a minimum version for CPAN modules hotly debated whenever the topic comes up: it won't matter what you choose; it's likely someone will disagree with it.

— Ken

Comment on Re^5: Deciding dependency versions Select or Download Code

Replies are listed 'Best First'.
Re^6: Deciding dependency versions by Bod (Parson) on Jun 11, 2023 at 16:40 UTC
v5.8.0 to 5.8.9 were more like a series of completely new releases I have seen a minimum version for CPAN modules hotly debated whenever the topic comes up: it won't matter what you choose; it's likely someone will disagree with it. Thanks Ken, That's given me the information and nudge I needed to make up my mind about the minimum Perl version...my default level of support for modules designed to run on the web and make API calls will be `v5.10`. That way, I don't need to start remembering (and more likely forgetting!) about sub-versions of `v5.8.x`. If I really need a newer feature then I will look at this again for just that module but until that happens or I write a module that isn't going to run on the web, that's one bit of decision making boxed off 😃 Perl version decided...now, that jut leaves dependency version But there is plenty of information in this thread for me to go over and digest...	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^6: Deciding dependency versions
by Bod (Parson) on Jun 11, 2023 at 16:40 UTC

v5.8.0 to 5.8.9 were more like a series of completely new releases

I have seen a minimum version for CPAN modules hotly debated whenever the topic comes up: it won't matter what you choose; it's likely someone will disagree with it.

Thanks Ken,

That's given me the information and nudge I needed to make up my mind about the minimum Perl version...my default level of support for modules designed to run on the web and make API calls will be v5.10. That way, I don't need to start remembering (and more likely forgetting!) about sub-versions of v5.8.x.

If I really need a newer feature then I will look at this again for just that module but until that happens or I write a module that isn't going to run on the web, that's one bit of decision making boxed off 😃

Perl version decided...now, that jut leaves dependency version
But there is plenty of information in this thread for me to go over and digest...

[reply]
[d/l]
[select]