Skip to content

Commit

Permalink
Update info on perl packages.
Browse files Browse the repository at this point in the history
  • Loading branch information
ssurbhi560 committed Jun 30, 2022
1 parent dfeab3a commit 7d15ca9
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions src/maintainer/knowledge_base.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1524,11 +1524,11 @@ Perl packages
Perl has three standard install locations: **core**, **vendor**, and **site**. Here, **core** is used only for the perl itself, **vendor** is used for installing any other conda-forge packages, and **site** is used for the user to install things locally from sources other than conda-forge.
The most commonly used build system for `perl packages <https://github.com/conda-forge/perl-file-which-feedstock>`__ is ``ExtUtils::MakeMaker``. For the archetypical packaging of packages of this form, you can have a look at `perl-file-which recipe <https://github.com/conda-forge/perl-file-which-feedstock/blob/main/recipe/meta.yaml>`__.
The most commonly used build system for `perl packages <https://github.com/conda-forge/perl-file-which-feedstock>`__ is ``ExtUtils::MakeMaker``. For typical packaging of packages of this form, you can have a look at `perl-file-which recipe <https://github.com/conda-forge/perl-file-which-feedstock/blob/main/recipe/meta.yaml>`__.
A few things to note in `perl-file-which recipe <https://github.com/conda-forge/perl-file-which-feedstock/blob/main/recipe/meta.yaml>`__ are:
A few things to note in the `perl-file-which recipe <https://github.com/conda-forge/perl-file-which-feedstock/blob/main/recipe/meta.yaml>`__ are:
* The ``name`` is composed of ``perl-`` **+** the lower-cased version of the CPAN name.
* The ``name`` is composed of ``perl-`` **+** the lowercase version of the CPAN name.
.. code-block::
Expand All @@ -1549,7 +1549,7 @@ A few things to note in `perl-file-which recipe <https://github.com/conda-forge/
run:
- perl
* The test section contains ``imports`` which lists the CPAN module that can be used in perl.
* The test section contains ``imports``, which lists the CPAN module that can be used in perl.
.. code-block::
Expand All @@ -1558,7 +1558,7 @@ A few things to note in `perl-file-which recipe <https://github.com/conda-forge/
- File::Which
The build section in the ``meta.yaml`` file should be something like this :
The build section in the ``meta.yaml`` file should be something like this:
.. code-block::
Expand All @@ -1571,8 +1571,8 @@ The build section in the ``meta.yaml`` file should be something like this :
- make test
- make install VERBINST=1
here the line with ``Makefile.PL`` is important as it guarantees installation into the vendor section, and it also helps in non-interference with the standard files by the ``NO_PERLLOCAL`` and ``NO_PACKLIST`` switches.
Notable here is ``INSTALLDIRS=vendor``, which selects the appropriate install location for a conda-forge package, and the ``NO_PERLLOCAL`` and ``NO_PACKLIST`` switches, which suppress various CPAN tracking files that are unnecessary when the module is being externally packaged via conda.
.. note::
``noarch: generic`` should be used only if the package is a pure perl package.
``noarch: generic`` should be used only if the package is a pure Perl package.

0 comments on commit 7d15ca9

Please sign in to comment.