Re: Has Pinto become broken for new installs? - bootstrapped cpanm cannot find Pinto

[stevieb]

A Perl module management system that appears out of date, with numerous open issues and with a broken security certificate may not be a good path forward.

Perhaps you could share what it is that you're trying to accomplish. There's very likely an alternate approach that you could use.

For example, I see you're using Linux, so with perlbrew, you can set up an instance exactly how you like, then simply clone the entire environment for consistency.

[Intrepid]

   Perhaps you could share what it is that you're trying to accomplish. … so with perlbrew, you can set up an instance exactly how you like …

My intention was to build a stack of the modules that are required at runtime by Dist::Zilla, which has many, many dependencies, in a separate environment. Because I've used Pinto on this CygPerl installation of mine to good effect, i.e. no issues, Pinto was my first thought. And then I got sucked in to finding out why I couldn't install Pinto now on the Linux box.

Perlbrew is very likely my next stop on this journey. The Linux system in question doesn't have Perlbrew installed yet, but another Linux system I maintain does, so I won't be completely without experience if I try that.

Thanks

Feb 04, 2026 at 19:08 UTC

[NERDVANA]

Shameless plug for my new CPAN::InGit. It solves roughly the same problem as Pinto, but with a drastically simpler strategy of just adding all the dist files to a git repo and then serving branches of that repo as individual darkpans. Fair warning, the module and its commandline tools are still pretty rough around the edges. But, it's good enough for production use of managing the modules used by my clients' projects.