Improbable. Removing Portable::HomeDir might break a script or an application, if that expects File::HomeDir's "portable" behaviour. OTOH having it in effect breaks scripts/apps that expect the "normal" behaviour. | [reply] |
I agree. People want to use the portable distribution because they want it portable. If I carry a Perl installation around on a memory stick, then it makes sense to have my_data on said stick.
berrybrew, on the other hand, is targeted at people who want to run different versions of Perl on the same machine. The Perls need to be isolated from each other, but not from the user/OS environment. In this case I would expect the "traditional" Windows implementation, if only because this is how perlbrew does it.
| [reply] |
Hey haj,
So you're saying berrybrew should go with the "Windows" method as opposed to the "Portable" one, yes?
This is the very first time I'm hearing about this situation, so I want to get as much input as I can so I can make the most flexible decision in the design.
I just released v1.19 yesterday and started a new dev branch, so if we can clear things up, I can get any changes into the next cut.
Could you have a read of my reply here, and let me know if what I've said as a possible solution makes sense?
Thanks,
-stevieb
| [reply] |
