4.8. How to handle RPM packages with Perls scripts

• perl-generators

  Automatically generates run-time Requires and Provides for installed Perl files. When you install a Perl script or a Perl module, you must include a build dependency on this package.

• perl-interpreter

  The Perl interpreter must be listed as a build dependency if it is called in any way, either explicitly via the perl package or the %__perl macro, or as a part of your package’s build system.

• perl-devel

  Provides Perl header files. If building architecture-specific code which links to the libperl.so library, such as an XS Perl module, you must include BuildRequires: perl-devel.

Procédure

• Apply the following syntax in your RPM SPEC file:

  BuildRequires: perl(MODULE)

  Copy to Clipboard Toggle word wrap
  Note

  Apply this syntax to Perl core modules as well, because they can move in and out of the perl package over time.

Procédure

• Use the perl(:VERSION) dependency with the desired version constraint in your RPM SPEC file:

  For example, to limit a package to Perl version 5.30 and higher, use:

  BuildRequires: perl(:VERSION) >= 5.30

  Copy to Clipboard Toggle word wrap

Procédure

• Include versioned MODULE_COMPAT Requires in RPM SPEC file for any package that delivers a Perl module:

  Requires:  perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))

  Copy to Clipboard Toggle word wrap