Front page | perl.perl5.porters |
Postings from March 2023
> On Mar 8, 2023, at 6:18 AM, Ovid <curtis.poe@gmail.com> wrote: > > git clone $some_repo > cd acme-kill-all-the-squirrels > perl-local switch . # my perl is now set to use the local perl-local setup > perl-local setup # builds Perl with proper config and version > # installs required cpan modules > <hack hack hack> > git commit -av > git push > > When I git push, I obviously don't want my CPAN modules or perl executable pushed, even if they're int he same directory. They're probably added to a .gitignore file. However, having the executable and CPAN modules in the same directory means that when I'm finished with this client, I can probably just rm -fr acme-kill-all-the-squirrels and I'm good to go. This not only keeps some paranoid clients happy, but I also don't have the usual hunting around on my computer trying to remember where custom stuff is installed. It's all in that one directory. FWIW: I have pretty much this exact workflow when working with plenv+Carton or perlbrew+Carton (or system-perl+Carton) but it requires having designed for that in my dev environment setup. When client's _haven't_ made sure they're supporting a process which is perl-install agnostic, that's when things get rough. Usually it's because they've organically grown their application for over a decade and "just didn't know better", which is fair … I'm not sure I was using Carton as heavily in 2013 as I am today. -ChrisThread Previous | Thread Next