Perl-Toolchain-Gang/Module-Build — comment on commit 886abd6b50511cc3183162817cae0fdfa18f060f
File:  line 0
By schwern:

Given the current reality of how `.modulebuildrc` mirrors the behavior of the command line and includes the special case of `Build.PL`, the documentation is handing the user a flawed method of setting install paths. Setting default install paths in `Build_PL` works just like passing them into `perl Build.PL` which is the safer way of doing it. Setting default install paths at `install` time *silently* overrides what the user might have passed to `perl Build.PL` and that's just wrong.

If you want to discuss changing how `Build_PL` behaves then open an issue about it, and if that gets changed we can change the docs to reflect that new reality, but don't write doc examples based on how it might possibly work in the future. The user has to cope with how it works right now.

If you want to discuss changing the order of how command line and modulerc defaults are handled to avoid the defaults blowing over `perl Build.PL` arguments, open an issue about it. That is probably the long term fix, but again, that doesn't mean we can't fix the docs for how reality works right now.

If you disagree and think that setting default install paths at `install` time is safer and more beneficial to the user using the current version of Module::Build, by all means argue that.