Upstream software project

perl-ExtUtils-InstallPaths

Build.PL install path logic made easy

About perl-ExtUtils-InstallPaths

Build.PL install path logic made easy

This project links 1 native package record across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

openSUSE Leap 15.6: 1 package records. Catalog coverage diagram, not an application screenshot.perl-ExtUtils-InstallPaths: recorded package coverageopenSUSE Leap 15.61 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
perl-ExtUtils-InstallPaths
Publisher
Not authoritatively mapped
Native package records
1
Operating systems
opensuse-leap-15-6
License expression
Artistic-1.0 or GPL-1.0+
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

This module tries to make install path resolution as easy as possible. When you want to install a module, it needs to figure out where to install things. The nutshell version of how this works is that default installation locations are determined from the ExtUtils::Config manpage, and they may be individually overridden by using the 'install_path' attribute. An 'install_base' attribute lets you specify an alternative installation root like _/home/foo_ and 'prefix' does something similar in a rather different (and more complicated) way. 'destdir' lets you specify a temporary installation directory like _/tmp/install_ in case you want to create bundled-up installable packages. The following types are supported by default. * * lib Usually pure-Perl module files ending in _.pm_ or _.pod_. * * arch "Architecture-dependent" module files, usually produced by compiling XS, the Inline manpage, or similar code. * * script Programs written in pure Perl. In order to improve reuse, you may want to make these as small as possible - put the code into modules whenever possible. * * bin "Architecture-dependent" executable programs, i.e. compiled C code or something. Pretty rare to see this in a perl distribution, but it happens. * * bindoc Documentation for the stuff in 'script' and 'bin'. Usually generated from the POD in those files. Under Unix, these are manual pages belonging to the 'man1' category. Unless explicitly set, this is only available on platforms supporting manpages. * * libdoc Documentation for the stuff in 'lib' and 'arch'. This is usually generated from the POD in _.pm_ and _.pod_ files. Under Unix, these are manual pages belonging to the 'man3' category. Unless explicitly set, this is only available on platforms supporting manpages. * * binhtml This is the same as 'bindoc' above, but applies to HTML documents. Unless explicitly set, this is only available when perl was configured to do so. * * libhtml This is the same as 'libdoc' above, but applies to HTML documents. Unless explicitly set, this is only available when perl was configured to do so.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Leap 15.6

  1. Package perl-ExtUtils-InstallPaths

    leap-15.6 (openSUSE Leap 15.6) (Development/Libraries/Perl): Build.PL install path logic made easy

    0.011-1.22: noarch

    Source: perl-ExtUtils-InstallPaths

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.