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

I think I'd prefer berrybrew removing the Portable::HomeDir by default. However, CPAN and cpanm both use File::HomeDir->my_home, which means it would be difficult to have different configs for different versions. This probably would only be a minor gotcha, but I see the impact would be greater than what I thought when I wrote this. A config directive is definitely a good idea.

Replies are listed 'Best First'.
Re^6: File::HomeDir strange behavior Perl 5.28
by stevieb (Canon) on Nov 02, 2018 at 20:53 UTC

    This is exactly why I wanted to hash this out in a public forum, to get as much feedback, criticism and "ohhh, I forgot about that angle!" comments that I can before I make a change.

    I don't like it when I'm too quick to implement something that I'll be kicking myself in the ass for in three months.

    Very good feedback so far here, I appreciate it all.

      I am not an expert user at all, but this is my experience so far removing (...\perl\vendor\lib\Portable\HomeDir.pm). In order to have <code>File::HomeDir->my_data giving me back the real Windows thing, my Perl installation has the following problem: installing new modules fires error: a new folder strawberry is created under C: where cpan or cpanm try to install the modules, failing. To get modules installed I have to recreate the original (...\perl\vendor\lib\Portable\HomeDir.pm).

        That's a pretty major setback that is, thanks for pointing it out.

        I haven't quite gotten to test this out for myself yet. I've been merging PRs and updating/correcting some other unrelated things for the impending inclusion of berrybrew into hurricup's Camelcade Perl5 Plugin for intelliJ IDEA IDE (which I use for almost all of my Perl development nowadays).

        Should be able to focus on the File::HomeDir situation sometime this week.