Re^3: berrybrew, the Perlbrew for Windows v1.30 released!

I see

It's also a lot less taxing (code and process time) doing quick registry reads than it is opening, reading, parsing, converting from and closing a JSON file on each run in C#.

Makes testing a whole lot easier as well.

Hmm, doubtful

It also ensures the configuration is always in a single, specific location, so it can be read and modified without having to figure out where the installation is located (by parsing and then searching each PATH for the berrybrew.exe binary, then loading the file from the data directory).

$HOME/.berrybrew is just as specific and doesn't require much figuring out

Comment on Re^3: berrybrew, the Perlbrew for Windows v1.30 released!

Replies are listed 'Best First'.
Re^4: berrybrew, the Perlbrew for Windows v1.30 released! by stevieb (Canon) on Dec 26, 2019 at 03:34 UTC
`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.	[reply] [d/l] [select]
Re^5: berrybrew, the Perlbrew for Windows v1.30 released! by ikegami (Patriarch) on Dec 28, 2019 at 14:38 UTC
Two users can't simultaneously be using two separate versions of Perl Sure they can. Screenshot of Task Manager showing two different users running two different versions of Perl This is due to how PATH env var works on Windows. If anything, Windows is more flexible than unix systems. The real difference is the lack of `cmd` startup script and lack of `cmd` functions. PowerShell might have those? If so, you could have a true perlbrew for PowerShell.	[reply] [d/l] [select]
Re^6: berrybrew, the Perlbrew for Windows v1.30 released! by stevieb (Canon) on Dec 28, 2019 at 16:24 UTC
"PowerShell might have those? If so, you could have a true perlbrew for PowerShell." I'll look into this, thanks!	[reply]
Re^4: berrybrew, the Perlbrew for Windows v1.30 released! by LanX (Saint) on Dec 26, 2019 at 03:10 UTC
It's not easy to tell what %HOME% means on Win. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}	[reply]
Re^5: berrybrew, the Perlbrew for Windows v1.30 released! by Anonymous Monk on Dec 26, 2019 at 05:40 UTC
LanX: It's not easy to tell what %HOME% means on Win. Nonsense.	[reply]