Tags:
create new tag
, view all tags

Contents

Motivation

This document describes the ID-BD internal policies and procedures related to Perl modules installation. Perl modules from the official RedHat repositories are either outdated or they are just not available. This issue prompted us to use rpm repositories like rpmforge or rpmfusion, where the quality control is less then optimal. Due to the missing or sloppy quality checks, the rpm packages containing some Perl modules generate rpm dependency errors. They require either Perl modules that are not yet available or libraries that are not offered by RedHat in the desired version. We created this policy to eliminate the rpm dependency problems related to Perl modules.

Perl modules source

The Perl modules are to be installed whenever possible from the official RedHat repositories. Although not all these repositories are provided by RedHat Inc itself, the following repositories are known to enforce a thorough quality check:

  • the official RedHat repositories
  • the EPEL repositories

This list of rpm repositories can be modified by adding other repositories that are committed to quality, or by removing a repository as the quality control degrades.

When a Perl module is not available from an official repository, that module is to be installed from CPAN.

Modules location

The Perl modules are installed in /instances/perl/. This directory is mounted from /instances.nfs/1/perl for the 32-bit machines, or from /instances.nfs/1/perl64 on the 64-bit machines.

The installation locations are NAS shares. These locations are mounted on all servers hosting web-instances.

Staging between perl-devel and perl CPAN repositories

The Perl modules installed in the productive environment must be tested first in the staging location.

TODO(Matteo) describe what testing means

How to install new modules

how to install a new module

test rpm availability

install from CPAN

how to test the installation

Updates

when to update

how to update

how to test the update

Logging changes

The changes to the module repositories must be logged in one of the following locations:

  • staging change log contains the changes made to the staging local repository
  • productive change log contains the changes made to the productive local repository.

Using the locally installed modules

TODO(Matteo or delegate) describe what needs to be done to use the local module repositories.

-- CristianTuduce - 2011-05-04

Topic revision: r4 - 2011-08-23 - tuduce
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback