Red Hat NETWORK SATELLITE 5.1.0 - CHANNEL MANAGEMENT Manual de usuario descargar pdf (Pagina 14)

http://www.rpm.org/RPM-HOWTO

http://www.redhat.com/docs/books/max-rpm/

http://www.rpm.org/mailing_list/

Pristine Sources

A crucial design goal of RPM is to allow the use of pristine software sources, as distributed

by the original authors of the software. With RPM, the pristine sources can be packaged,

along with any patches that were used, plus complete build instructions. This is an

important advantage for several reasons. For instance, if a new version of a program is

released, you do not necessarily have to start from scratch to make it compile. You can look

at the patch to see what you might need to do. All the compiled-in defaults and changes

made to get the software to build properly are easily visible using this technique.

Keeping sources pristine may seem important only to developers, but it results in higher

quality software for end users, as well.

1.2. RHN RPM Guidelines

The strength of RPM lies in its ability to define dependencies and identify conflicts accurately.

Red Hat Network relies on this aspect of RPM. Red Hat Network offers an automated

environment, which means that no manual intervention can take place during the installation of

a package. Therefore, when building RPMs for distribution through Red Hat Network, it is

imperative to follow these rules:

1. Learn RPM. It is crucial to have a fundamental understanding of the important features of

RPM to build packages properly. For more information about RPM, start with the following

resources:

• http://www.rpm.org/RPM-HOWTO/

• http://www.redhat.com/docs/books/max-rpm/

• http://www.rpm.org/mailing_list/

• http://fedora.redhat.com/participate/developers-guide/ch-rpm-building.html

2. When building an RPM for a child channel, build the package on a fresh install of Red Hat

Enterprise Linux of the same version as the child's base channel. Be sure to apply all

updates from Red Hat Network first.

3. The RPM package must install without using the --force or --nodeps options. If you cannot

install an RPM cleanly on your build system, Red Hat Network cannot install it automatically

on a system.

4. The RPM package filename must be in the NVR (name, version, release) format and must

contain the architecture for the package. The proper format is

name-version-release.arch.rpm. For example, a valid RPM package filename is

pkgname-0.84-1.i386.rpm, where name is pkgname, version is 0.84, release is 1, and arch

is i386.

5. The RPM package should be signed by the maintainer of the package. Unsigned packages

may be distributed through Red Hat Network, but the Red Hat Update Agent (up2date)

Chapter 3. Building Custom Packages

1 2 ... 9 10 11 12 13 14 15 16 17 18 19 ... 39 40

Sin comentarios

Red Hat NETWORK SATELLITE 5.1.0 - CHANNEL MANAGEMENT Manual de usuario Pagina 14