in reply to Re^4: File::HomeDir strange behavior Perl 5.28
in thread File::HomeDir strange behavior Perl 5.28

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.
  • Comment on Re^5: File::HomeDir strange behavior Perl 5.28

Replies are listed 'Best First'.
Re^6: File::HomeDir strange behavior Perl 5.28
by haj (Vicar) on Nov 02, 2018 at 13:11 UTC

    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]

        Yes, I read that article... With a new configuration option, everyone can have it their way... but the option needs to be implemented, documented, and maintained. If you just change the behaviour, it is more like perlbrew, "something" might break, but I can't think of any valid use case which breaks. If you keep it as it is, then it looks a bit weird for perlbrew users.

        Though I do use File::HomeDir and all sorts of Perls on Windows and therefore knew about the behaviour of the portable distribution, I am not affected at all. berrybrew is for testing, and while I'm testing, I use File::HomeDir::Test which avoids the problem.

        So, you might want to take that with a grain of salt: Personally, I'd prefer not having to bother with another switch for berrybrew install or a config option. Stuff like this tends to pile up and you'll never get rid of it again. Chose any behaviour, and if someone really has a valid use case (i.e. other than "hypothetically possible") then they can easily delete (or install) the Portable flavour of File::Homedir.

[reply]

In Section Seekers of Perl Wisdom