in reply to Module::Build- Overriding default $Config{installprefix}

Common thinko to upload personal config for general consumption. Solution is to edit Build.PL or try specify on commandline --install_path. There is support for ./cpan to do that non-interactive https://metacpan.org/pod/CPAN#Configuration-for-individual-distributions-(Distroprefs)
  • Comment on Re: Module::Build- Overriding default $Config{installprefix} (cpan Distroprefs )

Replies are listed 'Best First'.
Re^2: Module::Build- Overriding default $Config{installprefix} (cpan Distroprefs )
by Anonymous Monk on Aug 01, 2023 at 07:16 UTC

    Thanks for the clue of install_path.

    This did not work ...

    --install_path /some/dir/perl/etc

    ... needed to do ...

    --install_path etc=/some/dir/perl/etc

    ... "worked" in the sense installation did not fail due to permission error; have yet to try running the software. If that would still be a problem, then just /have to/ edit the damn installed file(s).

    All in all, setting various paths is damn fucking fiddly to install software in a user-controlled directory. Much less irritating was building own perl (& installing in user-controlled directory) and using that perl to install everything else. But decision is not mine to make :-|

      All that was for 💩

      _set_cfg_file sub in Astro::Catalog::Query::SkyCat searches for configuration file in equivalent of %ENV|$HOME|dirname($^X)/../etc (there is nice comment there about the last one).

      No message is produced by App::SourcePlot to set up a catalog file in HOME on the first run. On subsequent runs, using the Tk widget to use "default" catalog results on console ...

      Tk::Error: Unable to read catalog since no file specified and no defau +lt known. at /some/dir/perl/lib/perl5/Astro/Catalog.pm line 842. Tk callback for .toplevel1.frame1.menubutton.menu Tk::__ANON__ at /some/dir/perl/lib/perl5/x86_64-linux-thread-multi/Tk +.pm line 251 Tk::Menu::Invoke at /some/dir/perl/lib/perl5/x86_64-linux-thread-mult +i/Tk/Menu.pm line 532 <ButtonRelease> (command bound to event)

      👍

      Yes, I can _NOW_ shove the configuration files in HOME only after trying to debug the issue of not being able to specify a path for etc directory of *::Catalog.

      Much less irritating was building own perl (& installing in user-controlled directory) and using that perl to install everything else. But decision is not mine to make :-|

      Why is this decision not yours to make? In case it helps you make a case for building your own Perl, you might make some of the arguments mentioned recently here.