What are best practices for maintaining/testing (mostly Perl) software in separate git repositories with dependencies between them?

As the software is already CPAN-ready simply declare the test deps in the distro meta file. In other words think in terms of distributions, not repositories/branches I think you're lacking something like CPAN::Mini or DPAN, and a process of packaging and injecting the distros A branch should increase the version number, possibly using an underscore number or using the TRIAL distro name to indicate a non-stable release.

As the software is already CPAN-ready, simply declare the test deps in the distro meta file. In other words, think in terms of distributions, not repositories/branches. I think you're lacking something like CPAN::Mini or DPAN, and a process of packaging and injecting the distros.

A branch should increase the version number, possibly using an underscore number or using the -TRIAL distro name to indicate a non-stable release.

The PERL5LIB environment variable could be used to avoid adding temporary use lib statements to your scripts. Perlrun.

This doesn't really answer my question. Use lib is a minor issue. (And PERL5LIB isn't useful in taint mode, so it would not be useful for me anyhow.) – Rob Oct 27 at 9:38.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.