Dave Hodgkinson <daveh...@gmail.com> wrote: > Don't use system Perl. Brew your own and make it part of the app. >
I made a few bundles with Syntax::Collector. There's the ones that i use... - in all packages: strictures, autodie, feature, Carp, true - to change the syntax, like Method::Signatures (i keep them separate to make it more obvious that the syntax is not "system Perl", and to make it straightforward where to find these modules) - in Moo packages - for debugging Toddy <endonto...@googlemail.com> wrote: > Keep the exact versions of the module you're using in either your own CPAN > mirror or packaged with your self-brewed Perl to simplify consistency > across all of your environments. I'm thinking of using perlbrew + local::lib + Carton. It's slightly simpler to manage than my own CPAN mirror, and i think it does what i need. Plus i'm used to perlbrew and local::lib already, so i just have to learn Carton. David Cantrell <da...@cantrell.org.uk> wrote: > > If you do that it's a good idea to keep those packages, including the > package that contains your build of perl, reasonably up-to-date. This will > minimise the pain of upgrading (you'll just have to deal with occasional > small incompatibilities instead of a many-tentacled horror) and you'll also > have a procedure right from the start for dealing with upgrades, so when > you actually *need* to upgrade it won't be so fraught with peril. > Writing an upgrade procedure down sounds wise, it's noted. Does upgrading all dependencies every 2 months sound frequent enough, to avoid most cosmic-horrors? Or monthly? Either way i'll have an automatic reminder. I trust myself to do it when reminded. About the Prototype, i'm wondering whether to make one after my holidays in August. I'll speak about it face-to-face with Dave, first. I might post a message here later, maybe to ask further questions, or maybe to share what i've chosen to do in the end.