update module dependencies/requirements

[Lightning-]

this updates the module dependencies/requirements to recent versions of stdlib and concat

[saz]

Thanks for the PR! I'd prefer to not have any versions in the .fixtures.yml. Mind updating your PR?

What's the reason for concat >= 9.0.2?

[Lightning-]

Thanks for the PR! I'd prefer to not have any versions in the .fixtures.yml. Mind updating your PR?

no versions are fine too → updated

What's the reason for concat >= 9.0.2?

concat 9.0.0 is reasonable minimum (compatibility with stdlib 9) and 9.0.1 and 9.0.2 are harmless changes/fixes that everybody should simply apply 😆

[saz]

concat 9.0.0 is reasonable minimum (compatibility with stdlib 9) and 9.0.1 and 9.0.2 are harmless changes/fixes that everybody should simply apply 😆

The module isn't using any features of stdlib which is specific to v9 or newer. The same is true for concat. I don't see a good reason to raise the lower limit. Newer versions of both concat and stdlib will be used, if possible.

[Lightning-]

well i'd say that it's a good idea to force anything to go beyond stdlib 9 but don't wanna argue about that here; as long as fixtures aren't nailed to ancient anymore i'm good with that 😉

updated commit

[saz]

In general, I'm with you to force newer versions, but in some cases, it's just annoying people (and then potentially me 😄 ).

I'm curious, how are you managing modules and their dependencies?

[Lightning-]

I'm curious, how are you managing modules and their dependencies?

for the modules i write i'm absolutely merciless → go bleading edge or you possibly can't update 😉.
(but tbh, those modules (around 30) aren't public. at least yet, but i plan to push some of them into the world when i find time to do so).
not that i drop my sword instantly just because any update was released somewhere, but whenever i gotta do something in a module task#1 is to bring anything up-to-date. as well i'm usually pretty fast doing updates for the tools the modules manage (which includes packaging the tools from source instead of using distro-pkgs, if a non-bleading-edge-distro is used).

well ... i just hate code-rot and the spirit of "keep everything compatible as long as possible including preserving old/deprecated/... coding paradigms/patterns etc.". i blame a lazy update spirit for many of the problems in our it-world out there; admins and devs usually don't develop their stuff further just because they're bored, so people imho need to follow. being a linux system engineer and puppet engineer i see it as my job to actively maintain, update, refresh and rework my systems and my codes 😇.

for the modules i just use ... yeah well. trying to keep them as updated as possible unless version conflicts keep me off doing so. of course there's a grace period as people need to invest time/work/sweat/blood 😆. but to take the example of stdlib (and concat): stdlib 9 was released a year ago ... enough time to get the homework done.

of course it's hard to generalize but usually i tend to look forward rather than backward.