Re: berrybrew, the Perlbrew for Windows v1.15 released (wishlist)

Not sure if this comment is worth posting at berrybrew's homepage, therefore, here. To match sudo-less-ness of Perlbrew, maybe it's better to modify not "system", but "user" PATH environment variable. It was slightly discomforting :) to run berrybrew with elevated privileges. We are all admins at our Windows, but still... Also, a minor inconvenience (a bit untidy) was to find a .cpanm folder in the root of my C drive. The portable Strawberry Perl defines HOME environment variable to hide it.

OTOH, if the purpose of berrybrew was to install/manage Perls at system level regardless of logged-in user, then please ignore this comment :)

Comment on Re: berrybrew, the Perlbrew for Windows v1.15 released (wishlist) Download Code

Replies are listed 'Best First'.
Re^2: berrybrew, the Perlbrew for Windows v1.15 released (wishlist) by stevieb (Canon) on Jul 30, 2017 at 20:56 UTC
Thanks vr for the feedback. There was never any intention or desire to use an admin account, believe me. The issue stems from the fact that Windows forces the `SYSTEM` `PATH` over the `USER` one, and that causes problems. Any suggestions welcome on how to evade this in `C#` would be exceptionally welcome. This has been discussed numerous times outside of the issue tracker with those who are close to the project, as well as outside of it. As far as the `.cpanm` directory being in the root of `c:/`, I'll look into that. Normally it goes into the perl installation directory. Thanks for the note :) Normally though, this is directed by outside forces, so I'm not sure if it can be corrected within `berrybrew` or not. Again, I'll look into it. Always feel free to open an issue though. There are no good or bad issues, just ones that are taken seriously and will be responded to with respect and consideration. You have my word on that.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: berrybrew, the Perlbrew for Windows v1.15 released (wishlist)
by stevieb (Canon) on Jul 30, 2017 at 20:56 UTC

Thanks vr for the feedback.

There was never any intention or desire to use an admin account, believe me.

The issue stems from the fact that Windows forces the SYSTEM PATH over the USER one, and that causes problems. Any suggestions welcome on how to evade this in C# would be exceptionally welcome. This has been discussed numerous times outside of the issue tracker with those who are close to the project, as well as outside of it.

As far as the .cpanm directory being in the root of c:/, I'll look into that. Normally it goes into the perl installation directory. Thanks for the note :) Normally though, this is directed by outside forces, so I'm not sure if it can be corrected within berrybrew or not. Again, I'll look into it. Always feel free to open an issue though. There are no good or bad issues, just ones that are taken seriously and will be responded to with respect and consideration. You have my word on that.

[reply]
[d/l]
[select]