Perl Policy - ArchWiki

# Perl Policy

This page covers the policy for how perl itself is configured and packaged. For Perl module packaging guidelines, see Perl package guidelines.

## Introduction

This policy document was proposed, accepted, and implemented in version 5.10.0 of the perl package. It is the standard regarding to the perl package, related Perl packages, and creating Perl module packages (both in binary form and in the form of PKGBUILDs). Portions are derived from the Debian Perl Policy document and from various portions of the Perl man pages.

### 5.10 caveats

NOT TRUE: The directories for scripts do not conform to the Filesystem Hierarchy Standard (FHS).

Note: The FHS describes what directories must be in `/usr/bin` and does not prohibit adding other directories.

### Reasoning

Apparent problems with pre-5.10.0 perl packaging conventions included:

1. The current Arch Linux default perl installation installs site and vendor packages into the same directory tree, which frequently causes conflicts if the end user installs and upgrades Arch Linux perl (vendor) packages on top of site packages.
2. The current Arch Linux default perl installation installs updates to core modules into the perl core directories, creating file conflicts. Examples include modules such as `Data::Dumper` and `version`.
3. A symlink-farm is created in `/usr/lib/perl5/` and `/usr/lib/perl5/site_perl` which is un-necessary and confusing.
4. A number of standard modules seem to be missing, or were neglected to be added as provides in the perl package itself, causing confusion and redundant entries in AUR and Community as users try and fix the apparent problem of missing modules, which are provided by perl. This is probably a matter of education.
5. Current perl-module PKGBUILD's could be simplified and standardized quite a bit.

This policy would eliminate all these problems.

### Pitfalls

Current (apparent) downsides to adopting a policy such as this one:

1. An update of every perl module PKGBUILD so that it installs into the correct (vendor) directory tree. It remains somewhat backwards-compatible with the old structure, in that old PKGBUILD's would technically work.
2. Introduces changes into the `perl` package, which lives in the core repository, and proposes a new `perl-modules` package, which would live in the extra repository.
3. Non-perl packages which compile static copies of the perl interpreter will not operate correctly until recompiled on an Arch Linux PC which adheres to this document. Examples of such packages include `vim`, `subversion`, and `irssi`. Many such examples exist.

## Perl versions

At any given time, the package `perl` should represent the current stable upstream version of Perl revision 5. (see Perl 6).

Only one package may contain the `/usr/bin/perl` binary and that package must either be perl or a dependency of that package. In order to provide a minimal installation of Perl for use by applications without requiring the whole of Perl to be installed, the `perl` package contains the binary and a basic set of modules. The perl package should declare provide statements for every module provided by the base perl package.

## Module paths

Perl searches three different locations for modules, referred to in this document as core in which modules distributed with Perl are installed, vendor for packaged modules, and site for modules installed by the local administrator.

The module search path (`@INC`) in the Arch Linux packages has been ordered to include these locations in the following order:

- site

Modules installed by the local administrator for the current version of Perl. Typically, these modules are installed using the cpan or cpanp tool, or are downloaded in source form and installed via make.

  `/usr/lib/perl5/site_perl/version`
  `/usr/share/perl5/site_perl/version`

- vendor

Packaged modules, installed via the pacman tool from the core, extra, or community repositories, or built into proper Arch Linux packages from ABS/AUR PKGBUILDs.

  `/usr/lib/perl5/vendor_perl`
  `/usr/share/perl5/vendor_perl`

- core

Modules included in the core Perl distribution.

  `/usr/lib/perl5/core_perl`
  `/usr/share/perl5/core_perl`

- obsolete

Obsolete is the path name to modules installed prior to the establishment of this document. These paths have been removed from @INC in perl 5.12.2.

  `/usr/lib/perl5/site_perl/current/arch`
  `/usr/lib/perl5/site_perl/current`
  `/usr/lib/perl5/current`

In each of the directory pairs above, the `lib` component is for binary, architecture dependent (XS) modules, and `share` for architecture-independent (pure-perl) modules. Under no circumstances should `current` be used as a replacement for `version`. Core and Vendor modules should be matched to the current installation of perl.

## Documents

The POD files and manual pages and HTML documentation which do not refer to programs may be stripped from the package, which is normal for most Arch Linux packages in general. This is optional.

Manual pages distributed with Perl packages must be installed into the standard directories:

Programs
  Manual pages for programs and scripts are installed into `/usr/man/man1` with the extension `.1perl`.

Modules
  Manual pages for modules are installed into `/usr/man/man3` with the extension `.3perl`.

## Binaries and scripts

In order to prevent file collisions, it is important to keep binaries generated by core, vendor, and site installs separate. It is also important that the default `PATH` environment variable set in each users profile to search for binaries in the same order as perl's `@INC` path. In order to accomplish this, binaries should be installed into the following directories:

Core
  Binaries and scripts for all core packages should be installed into `/usr/bin/core_perl`.
Vendor
  Binaries and scripts for all vendor packages should be installed into `/usr/bin/vendor_perl`.
Site
  Binaries and scripts for all site should default to be installed into `/usr/bin/site_perl`.

The `perl` package should include a mechanism to adjust end-users `PATH` entries accordingly so that perl binaries are searched for in the following order: site, vendor, core.

## Core

Core modules are Perl modules "typically" included in the core Perl distribution.

### Core directories

- Modules included in the core Perl distribution should be installed into `/usr/lib/perl5` and `/usr/share/perl5`.
- Only modules contained in the `perl` package should be installed into this directory tree.
- No version subdirectory exists in these paths as the dependencies for packaged modules should ensure that all work with the current `perl` package.

### Core perl packages

The `perl` package should contain the `/usr/bin/perl` binary, and a minimal set of modules needed in order for simple perl scripts to run and for a base system to operate. It should be maintained in the core repository.

The following is a list of a few modules (for example), which are provided in the perl package. (See the PKGBUILD for the official list).

`'perl-checktree' 'perl-collate' 'perl-config' 'perl-cwd' 'perl-dynaloader' 'perl-english' 'perl-env' 'perl-exporter' 'perl-fnctl' 'perl-filehandle' 'perl-find' 'perl-finddepth' 'perl-getopt' 'perl-makemaker' 'perl-socket' 'perl-sys-syslog' 'perl-db-file' 'perl-storable' 'perl-data-dumper' 'perl-digest-md5'`.

Every module supplied in the perl package shall be added into the `provides` array in the PKGBUILD. Modules in this array should NOT appear in the perl packages `conflicts` or `replaces` arrays. End users should be able to install newer versions of core modules, either in vendor or site directories without file collisions.

## Site

Site modules are perl modules installed by the local administrator for the current version of Perl. Typically, these modules are installed using the cpan tool, or are downloaded in source form and installed via make (or MakeMaker).

### Site directories

The Perl packages must provide a mechanism for the local administrator to install modules under `/usr/lib/perl5/site_perl` but must not create or remove those directories.

Modules should be installed to the directories described above in Module Path `site`, programs to `/usr/bin/site_perl` and manual pages under `/usr/man`.

### Site installation

The following commands should be sufficient in the majority of cases for the local administrator to install modules and must create directories as required:

    perl Makefile.PL
    make install

or

    cpan Foo::Bar

## Vendor

Vendor modules are packaged modules, installed via the pacman tool, or modules which have been built into proper Arch Linux packages from a PKGBUILD and makepkg.

### Package naming

Perl module packages should be named for the primary module provided. The naming convention for module Foo::Bar is perl-foo-bar. Packages which include multiple modules may additionally include provides for those modules using the same convention.

### Vendor directories

The installation directory for Arch Linux modules must be different from that for `site` modules. Some guidelines include:

- The current Perl packaging uses the vendor directories for this purpose, which are at present as described in above as `vendor`.
- No version subdirectory exists on these directories as the dependencies for packaged modules should ensure that all work with the current `perl` package.
- The Perl distribution includes many modules available separately from CPAN, which may have a newer version. The intent of the `@INC` ordering (described above) is to allow such modules to be packaged to vendor which take precedence over the version in core. A packaged module which shadows a core module in this way must be a newer version.
- Module packages must install manual pages into the standard directories using the extensions `.1p` and `.3pm` to ensure that no conflict arises where a packaged module duplicates a core module.
- `.packlist` (used for module uninstalls) and `perllocal.pod` (used to record local/site installations) files should not be installed, and should be removed from the package if found.
- Empty directories should be pruned.

### Vendor installation

A module should use the following lines in the PKGBUILD build target.

    perl Makefile.PL INSTALLDIRS=vendor

and this one to install the results into the temporary tree...

    make install DESTDIR="${pkgdir}" install

A depends on perl (>= 5.10.0) is required in order ensure that the module is correctly installed into the new `@INC` path.

### Sample vendor PKGBUILD

    # $Id$
    # Contributor: Barry User <barry@user.com>
    # Maintainer: Harry Hacker <harry@hacker.com>

    pkgname=perl-html-template
    _realname=HTML-Template
    pkgver=2.9
    pkgrel=2
    pkgdesc="Perl/CPAN Module HTML::Template : a simple HTML templating system"
    arch=('any')
    url="http://search.cpan.org/dist/${_realname}/"
    license=('GPL' 'Artistic')
    depends=('perl>=5.10.0')
    source=("http://www.cpan.org/authors/id/S/SA/SAMTREGAR/${_realname}-${pkgver}.tar.gz")
    md5sums=("cbf88a486b36284be55765ac7357c187")
    options=('!emptydirs')

    build() {
      cd "${_realname}-${pkgver}"

     # Setting these env variables overwrites any command-line options we don't want...
     export PERL_MM_USE_DEFAULT=1 PERL_AUTOINSTALL=--skipdeps \
       PERL_MM_OPT="INSTALLDIRS=vendor DESTDIR='$pkgdir'" \
       PERL_MB_OPT="--installdirs vendor --destdir '$pkgdir'" \
       PERL5LIB="" PERL_LOCAL_LIB_ROOT="" \
       MODULEBUILDRC=/dev/null

     # If using Makefile.PL
     { /usr/bin/perl Makefile.PL &&
       make &&
       make test &&
       make install; } || return 1

     # If using Build.PL
     { /usr/bin/perl Build.PL &&
       ./Build &&
       ./Build test &&
       ./Build install; } || return 1

     # remove perllocal.pod and .packlist
     find "$pkgdir" -name .packlist -o -name perllocal.pod -delete
    }

### Dependencies

#### Binary modules

Binary modules must specify a dependency on either `perl` with a minimum version of the `perl` package used to build the module, and must additionally depend on the expansion of `perlapi-$Config{version}` using the `Config` module.

#### Architecture-independent modules

Architecture-independent modules which require core modules from the `perl` package must specify a dependency on that package.

Modules which contain explicit `require version` or `use version` statements must specify a dependency on `perl` with the minimum required version, or more simply the current version.

In the absence of an explicit requirement, architecture-independent modules must depend on a minimum `perl` version of `5.10.0` due to the changes in `@INC` introduced by that version.

## Perl6

There is currently work in progress on the next major revision, although the specifications have yet to be finalised.

It is anticipated that when Perl 6 is released it will initially be packaged as perl6, install the binary as `/usr/bin/perl6`, and use different directories for packaged modules to perl:

  `/usr/lib/perl6`
  `/usr/share/perl6`

This will allow Perl 5 and 6 packages and modules (which should be packaged as perl6-foo-bar), to coexist for as long as required.

At some stage in the future when Perl 6 is sufficiently mature, the package naming may be reversed such that the `perl` package contains Perl 6 and the current package becomes `perl5`.

Category:

- Package development