"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.

In reply to Re^3: Strawberry Perl - installing an older version (berrybrew) by stevieb
in thread Strawberry Perl - installing an older version by kcott

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.