Build.PL of Astro::Catalog module has near the end ...

etc_files => { 'etc/skycat.cfg' => 'etc/skycat.cfg', 'etc/sss.cfg' => 'etc/sss.cfg', }, install_path => { 'etc' => File::Spec->catdir($Config{installprefix}, 'etc'), },

That $Config{installprefix} is /usr here, which a non-superuser cannot modify. As I am trying to build as non-superuser, that results in ...

... All tests successful. Files=27, Tests=3453, 15 wallclock secs ( 0.19 usr 0.05 sys + 11.09 c +usr 1.56 csys = 12.89 CPU) Result: PASS GSB/Astro-Catalog-4.37.tar.gz ./Build test -- OK Running Build install for GSB/Astro-Catalog-4.37.tar.gz Building Astro-Catalog !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! +!! ERROR: Can't create '/usr/etc' mkdir /usr/etc: Permission denied at /usr/share/perl5/vendor_perl/ExtU +tils/Install.pm line 489. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! +!! at /some/dir/perl/lib/perl5/Module/Build/Base.pm line 3576. GSB/Astro-Catalog-4.37.tar.gz ./Build install -- NOT OK Stopping: 'install' failed for 'Astro::Catalog'.

Setting {install_base,prefix,installprefix} had not help yet. What could I be missing?

# Environment. # Setting *prefix here only because of the "$Config{installprefix}". PERL_MB_OPT=--install_base '/some/dir/perl' --config installprefix='/s +ome/dir/perl' --config prefix='/some/dir/perl' PERL_MM_OPT=INSTALL_BASE='/some/dir/perl' PREFIX='/some/dir/perl' # In the .cpan/build directory. grep -C 1 -r 'install|prefix' _build | grep -v orig _build/build_params- { _build/build_params: 'prefix' => '/some/dir/perl' _build/build_params- }, -- _build/build_params- 'include_dirs' => [], _build/build_params: 'install_base' => '/some/dir/perl', _build/build_params: 'install_base_relpaths' => {}, ## "/usr" did not change. _build/build_params: 'install_path' => { _build/build_params- 'etc' => '/usr/etc' _build/build_params- }, _build/build_params: 'install_sets' => {}, _build/build_params: 'installdirs' => 'site', _build/build_params- 'libdoc_dirs' => [ -- _build/build_params- 'perl' => '/usr/bin/perl', -- _build/build_params- 'pollute' => undef, _build/build_params: 'prefix' => undef, _build/build_params: 'prefix_relpaths' => {}, _build/build_params- 'prereq_action_types' => [ -- _build/runtime_params- 'config' => { _build/runtime_params: 'prefix' => '/some/dir/perl +' _build/runtime_params- }, _build/runtime_params: 'install_base' => '/some/dir/perl', _build/runtime_params- 'verbose' => '1'

In reply to Module::Build- Overriding default $Config{installprefix} by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.