Re^2: how to improve: use MODULE VERSION LIST

Thanks 1nickt.

Yeah, I have been coaching folks to do the use lib 'new dir' technique, to rearrange @INC. Which works okay when used in combination with "use autodie 2.29".

What bothers me most is that I have to manipulate @INC at all, especially when specifying a VERSION that I'm looking to use. The real problem is that Perl will not keep looking for the newer version of a module, if an older one is found earlier in the @INC list of locations.

Smile,
Steve

Comment on Re^2: how to improve: use MODULE VERSION LIST

Replies are listed 'Best First'.
Re^3: how to improve: use MODULE VERSION LIST by 1nickt (Canon) on Jan 07, 2017 at 22:00 UTC
That's not how it should be working. If you have a newer version of a module in a directory that you add with `use lib`, that should be the one loaded, without need of a version number (so long as that's the last change you make to `@INC`). You should be able to do: `$ perl -Mautodie -E 'say $autodie::VERSION' 2.23 $ perl -I/usr/foss/packages/foss-perllib -Mautodie -E 'say $autodie::V +ERSION' 2.29` [download] The way forward always starts with a minimal test.	[reply] [d/l] [select]
Re^3: how to improve: use MODULE VERSION LIST by RonW (Parson) on Jan 10, 2017 at 03:34 UTC
As I mentioned in my previous post, I think it would be better to have separate installations of Perl, each with the required set modules of the required versions, with a development installation that is kept up to date. When a new application moves to production, make a new installation of Perl for it and install the modules it needs. this way, each application can have the version of Perl and whatever modules it needs, without worrying about the needs of other applications.	[reply]