view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

  - internal refactor, Dist::Zilla, perlcritic, etc. (gh#15)

1.08 2019-11-25 08:36:38 -0700
  - Added alien_install_type property (gh#14)

1.07 2019-11-22 16:01:56 -0700
  - Fix bug in blib detection (gh#13)
  - Update documentation to reflect defaults for %s (gh#12, gh#13)

1.06 2018-12-15 20:34:11 -0700
  - Require Archive::Tar 1.40 for pax_global_header fix

1.05 2018-08-29 16:53:39 -0400
  - Documentation improvements
  - Improve diagnostics for HTTP connection failures (gh#6, gh#7)

1.04 2018-06-06 09:00:21 -0400
  - ALIEN_INSTALL_TYPE is now fully compatible with Alien::Build
    Previously there were some edge cases with setting it to
    'default'

lib/Alien/Base/ModuleBuild/API.pod  view on Meta::CPAN

=item alien_version_check

[version 0.001]

A command to run to check the version of the library installed on the system. The default is C<pkg-config --modversion %n>.

=back

=head2 PACKAGE AND ENVIRONMENT VARIABLES

A few global variables are used to set gross behavior. For each pair of variables, if both are set, the environment variable takes precedence.

=over

=item $ENV{ALIEN_ARCH}

[version 0.017]

Setting this changes the default for alien_arch above.  If the module specifies its own alien_arch in its C<Build.PL> file then it will override this setting.  Typically installing into an architecture specific directory is what you
want to do, since most L<Alien::Base> based distributions provide architecture specific binary code, so you should consider carefully before installing modules with this environment variable set to 0.  This may be useful for
integrators creating a single non-architecture specific RPM, .deb or similar package.  In this case the integrator should ensure that the Alien package be installed with a system install_type and use the system package.