in reply to Re^2: Module::Build Build.PL parameter inserted by Module::Starter - fatal error
in thread Module::Build Build.PL parameter inserted by Module::Starter - fatal error

G'day Intrepid,

"Sorry, I'm afraid I don't recall. It was several weeks ago and it has scrolled off my bash history. Whatever I did, I ended up with both a Makefile.PL and a Build.PL file. Let's see ... just tested it, yeah, you can do that by providing both --eumm and --mb on the commandline. I must have done that?"

Check your ~/.module-starter/config file. I have:

ken@titan ~/.module-starter $ cat config | grep build builder: ExtUtils::MakeMaker

The builder entry takes a space-separated list. Perhaps you have something like this:

builder: ExtUtils::MakeMaker Module::Build

I believe that would cause the "ended up with both a Makefile.PL and a Build.PL file" situation.

— Ken

Replies are listed 'Best First'.
Re^4: Module::Build Build.PL parameter inserted by Module::Starter - fatal error
by Intrepid (Curate) on Sep 18, 2025 at 17:19 UTC
    Ken wrote:
    Check your ~/.module-starter/config file

    I didn't have such a file, I just starting in using module-starter without any config, just cli options. I've created one now, it's a good idea to have your prefs be consistent from one usage to another.

    Thanks for taking the time to comment.

    I'm gonna point out that there's a spec that recommends a filesystem location for config files. Quoting:

    $XDG_CONFIG_HOME defines the base directory relative to which user-specific configuration files should be stored. If it is either not set or empty, a default equal to $HOME/.config should be used.

    It's probably the least observed of the recommendations in that document; it's a widely defaulted-to convention to locate a dotfile or dotdir directly under the user's HOME. But after awhile this fills up ~ with many config files/dirs and arguably this is not a good thing.

        — Soren

    Sep 18, 2025 at 17:18 UTC