berrybrew is not meant to be a user-specific software, it's system wide, so there's not much sense in placing a configuration file inside of a user's home directory. This is due to how PATH env var works on Windows. Two users can't simultaneously be using two separate versions of Perl, so I don't see much sense having multiple instances of berrybrew floating around (ie. instance per user). The system paths takes precedence over user paths, so if someone installs Active or Strawberry Perl as a system perl, none of the berrybrew perls would take effect. This is unlike Unix, which is why Perlbrew can work the way it does (per user).

That said, I'm not even a Windows user, I use it only for developing this software, so if you have any suggestions on how to make it better, I'm all ears.

Might I ask what it is you have against using the registry? I'm legitimately curious. I'm always interested in hearing from others in order to make my software better.

Update: I would love to learn how to make it so that A) it would work per user, and B) refreshing the environment on each change wasn't necessary. I have tried repeatedly to achieve these goals, but obviously, to no avail.

In reply to Re^4: berrybrew, the Perlbrew for Windows v1.30 released! by stevieb
in thread berrybrew, the Perlbrew for Windows v1.30 released! by stevieb

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.