Hacker News Reader

That still allows your deps to be stateful and out-of-band of the build. I'd prefer the build to be exclusively aware of version numbers in one place and let the code be version agnostic.

I'm not a Perl user, I don't consider running sed on my source code to be a "bonus".

Still better than Go though.

View on HN

There are a number of tools in Perl that will scan your code base and automatically generate a dependency list based on what it finds. The one I use is called Dist::Zilla (http://dzil.org/), and it automates the entire packaging and library release process. Again, this is how civilized languages work.

I'm sure Perl isn't unique here, of course.

> I'm not a Perl user, I don't consider running sed on my source code to be a "bonus".

That was completely unnecessary.

How else do you deal with all the import invocations in the source code files with outdated versions?

M4? Make + C preprocessor? Perl generating Perl? I tried to guess the least-absurd option for updating a library.

Please inform the rest of us what the standard tooling for handling this in the Perl community is.

Of course. A true Perl user has no need for sed, when there's "perl -pi -e".

Reply on news.ycombinator.com