in reply to Re: Strawberry Perl - installing an older version
in thread Strawberry Perl - installing an older version

G'day stevieb,

Thanks for the reply. I have some questions.

The links you've provided are for an "unreleased, currently being worked on" version. Is there a "released, finished being worked on" version?

I see "... the list of Strawberry Perls available ..." mentioned in the opening remarks, in the available and fetch commands, and in the "Update Perls Available" section. I'm unclear as to what this actually refers. Are all versions on "Strawberry Perl Releases" available? Does "we'll update the local perls.json file" refer to something that berrybrew does dynamically, or an indication of something that will be made available in some later release?

In the "Configure Root Directory" section, I'm concerned about "This feature is incomplete ... things don't get properly reset yet.". I'll hold off further comment on that until I hear about the "released, finished being worked on" version that I asked about above.

I have a number of Perls installed on my machine: an ActivePerl and a Strawberry Perl already mentioned in the OP; I have Git Bash which installed its own Perl; Cygwin which also has its own Perl; and Perlbrew Perls. Are any of these affected by berrybrew?

— Ken

Replies are listed 'Best First'.
Re^3: Strawberry Perl - installing an older version (berrybrew)
by stevieb (Canon) on Mar 10, 2020 at 17:00 UTC
    "Is there a "released, finished being worked on" version?"

    Of course! ...here. The version I referred you to is stable and is deemed for release after some doc updates I didn't get done earlier this year.

    "I see "... the list of Strawberry Perls available ..." mentioned in the opening remarks, in the available and fetch commands, and in the "Update Perls Available" section. I'm unclear as to what this actually refers. Are all versions on "Strawberry Perl Releases" available? Does "we'll update the local perls.json file" refer to something that berrybrew does dynamically, or an indication of something that will be made available in some later release?"

    That refers to newer releases as Strawberry publishes them. 5.34 for example would be added to what berrybrew deems as available as soon as Strawberry builds, releases and adds it to the release list. This isn't added to berrybrew's internal list automatically. I never assume a user has Internet access, so when a new release of Perl is cut, Strawberry follows shortly thereafter, which is when berrybrew fetch is used.

    "In the "Configure Root Directory" section, I'm concerned about "This feature is incomplete ... things don't get properly reset yet.". I'll hold off further comment on that until I hear about the "released, finished being worked on" version that I asked about above."

    That section refers to people who want to move their Perl installation directory to somewhere that wasn't used when berrybrew was initially set up. This isn't used often at all. I'm going to move that section to a different document. Most users will never need to do this.

    "I have a number of Perls installed on my machine: an ActivePerl and a Strawberry Perl already mentioned in the OP; I have Git Bash which installed its own Perl; Cygwin which also has its own Perl; and Perlbrew Perls. Are any of these affected by berrybrew?"

    Nope, not at all. In fact, you can add them as a berrybrew managed perl by using the berrybrew virtual command if desired though. All that means is that you can switch back and forth to them as easily as the other berrybrew perls. Nothing is done to the file system at all. It's all done with PATH manipulation. If berrybrew is disabled or removed, everything goes back to normal.

[reply]
[d/l]
[select]

      Thanks for the comprehensive response. I believe that addresses all of my questions.

      — Ken

[reply]

In Section Seekers of Perl Wisdom