in reply to Re: New berrybrew installer; Looking for testers
in thread New berrybrew installer; Looking for testers
Thank you for this.
I should have made note about previous installs.
A side effect I didn't consider is that internally, I call berrybrew unconfig but not using the full path, so it likely used the existing 1.22 berrybrew, which would have blown away the original PATH. Probably that's the reason the new path wasn't added as well.
Was there any indication as to why the malware software caught it? I don't use Windows except for developing berrybrew and testing things for a few Windows-based clients I have.
If your 1.22 version was using C:\berrybrew as its Perl instance directory, re-adding that version to PATH should fix things right up. If you want to carry on with the new version, it will happily use your old instances, or the new 5.30.0 instance you installed as part of the test (using berrybrew switch $version). The new 1.27 is backwards compatible with 1.22. It just has many new features and error checking.
I'm still working out kinks. This is my first time creating a Windows installer :)
Again, thanks. Very helpful feedback.
|Replies are listed 'Best First'.|
Re^3: New berrybrew installer; Looking for testers
by swl (Priest) on Nov 23, 2019 at 01:23 UTC
by stevieb (Canon) on Nov 23, 2019 at 01:38 UTC
by swl (Priest) on Nov 23, 2019 at 02:24 UTC