NAME

RPM::Constants - Groups of RPM-defined symbols

SYNOPSIS

use RPM::Constants qw(:rpmerr :rpmtype);

DESCRIPTION

This package is a collection of the constants defined by rpm itself that may be of use to those developing with the RPM Perl bindings.

GROUPS

For ease of use and uderstanding (at last count, the total number of constants was 232), the constants are broken up into several smaller groups:

Header Tag Identifiers

The following symbols may be imported via the tag :rpmtag, and represent the various elements that may be present in a package header. When used to retrieve data from a header as a hash key, the RPMTAG_ portion should be omitted from the name. Use the full name only when referring to the constant. Note that each name is followed by either a $ or a @. This signifies the return type of the data; a scalar or an array reference. In all cases, a failed operation is noted by a return value of undef.

The majority of the tags that return list references in fact refer to the ordered list of files present in the BASENAMES tag. In these cases (such as MD5SUMS), the value of the array at a given point may be null if it is not relevant. That is because the BASENAMES array (and thus all other file-related lists) must accomodate the indices at which a directory name is specified for the sake of defining the directory. In such cases, values such as size or MD5 checksum have no direct relevance.

RPMTAG_ARCH ($)

Name of the architecture that the package was built for. If the package is architecture-independant, the value should read "noarch".

RPMTAG_ARCHIVESIZE ($)

Size of the archive portion of the file. RPM stores the archive portion of a (non-source) package as a cpio archive, which may also be compressed internally. Thus, this value is generally larger than the file size of the RPM file itself.

RPMTAG_BASENAMES (@)

A list of the base (leaf) names of the files contained within the package. These are combined with the values from RPMTAG_DIRNAMES using a mapping provided by RPMTAG_DIRINDEXES.

This is actually a very key tag within a header. Many of the list-returning tags documented further down maintain a one-to-one correlation with the elements in this array.

RPMTAG_BUILDARCHS (@)

Not entirely sure. Appears from source code examples to be a list of those architectures for which a package should be built. All examples from the set of SRPMs in Red Hat Linux 6.2 only use this tag when the only value is noarch.

RPMTAG_BUILDHOST ($)

Name of the host the package was built on.

RPMTAG_BUILDMACROS (@)

This does not seem to be used in the library. It may be present for future expansion use.

RPMTAG_BUILDROOT ($)

Specifies the root at which the package is built.

RPMTAG_BUILDTIME ($)

The time/date when the package was created, expressed as a time() value (seconds since the epoch).

RPMTAG_CHANGELOGNAME (@)

RPMTAG_CHANGELOGTEXT (@)

RPMTAG_CHANGELOGTIME (@)

These three items should be taken together. Each should have the same number of items, and the items at corresponding indices should be taken together. Taken this way, they provide a small-scale changelog for the package, detailing the name of the person making the entry, the text of the entry and the time of the entry, in the respective order given above.

RPMTAG_CONFLICTFLAGS (@)

RPMTAG_CONFLICTNAME (@)

RPMTAG_CONFLICTVERSION (@)

These three items are used in conjunction to specify packages and/or individual files which the package itself would conflict with. Of the three, only RPMTAG_CONFLICTNAME is required to have data in all elements of the array. The other two will have the same number of elements, though some (or most) may be null. This is the same approach as is used to specify the elements that the package obsoletes, those the package provides and those the package requires (see "Three-Part Linkage" below).

RPMTAG_COPYRIGHT

Maintained by RPM for backwards-compatibility with some older packages. It is the same as RPMTAG_LICENSE.

RPMTAG_COOKIE ($)

A simple tag, a single text string, added at the time the RPM is created. Generally, it is created from the hostname on which the package is built and the UNIX time() value at the time of packaging.

RPMTAG_DESCRIPTION ($)

A textual description of the package.

RPMTAG_DIRINDEXES (@)

This data should have a one-to-one correspondance with RPMTAG_BASENAMES, above. Each item here is a numerical index into the list of directories named in RPMTAG_DIRNAMES below. It indicates which of the directories is to be prepended to the corresponding base file name in order to create the full pathname.

RPMTAG_DIRNAMES (@)

This is a list of all directories into which the package would install files. This list is used with RPMTAG_BASENAMES to create full paths, indexed by way of RPMTAG_DIRINDEXES above.

RPMTAG_DISTRIBUTION ($)

A text label identifying the name given to the overall larger distribution the package itself is a part of.

RPMTAG_EXCLUDEARCH (@)

A list of architectures for which the package should not be built.

RPMTAG_EXCLUDEOS (@)

A list of operating systems for which the package should not be built.

RPMTAG_EXCLUSIVEARCH (@)

A list of architectures only for which the package should be built.

RPMTAG_EXCLUSIVEOS (@)

A list of operating systems only for which the package should be built.

RPMTAG_FILEDEVICES (@)

The integer device values (from the stat system call) for each file in the package.

RPMTAG_FILEFLAGS (@)

A bit-field with zero or more of the flags defined below under the heading of rpmfile. See the flags themselves for more detail.

RPMTAG_FILEGROUPNAME (@)

A string-array data field that contains the group ID (by name) that should be used for setting group ownership of the files contained in the package. There should be a one-to-one correspondance between this list and the list of files in RPMTAG_BASENAMES. See also RPMTAG_USERNAME.

RPMTAG_FILEINODES (@)

The inode (from the stat system call) that each file in the package had on the system on which the package was built.

RPMTAG_FILELANGS (@)

Used to specify language-specific files, which may then be marked for skipping based on the list of accepted languages at install-time.

RPMTAG_FILELINKTOS (@)

A list of names with exactly as many elements as there are filenames; each slot in this list is either empty, or (if not) gives the name of a file that the current filename should be made as a symbolic link to.

RPMTAG_FILEMD5S (@)

MD5 checksums for each file in the package.

RPMTAG_FILEMODES (@)

The file-modes as integer values, for each file in the package.

RPMTAG_FILEMTIMES (@)

The integer modification-time (from the stat system call) for each file in the package.

RPMTAG_FILERDEVS (@)

The integer rdev values (from the stat system call) for each file in the package.

RPMTAG_FILESIZES (@)

The size (in bytes) of each file in the package.

RPMTAG_FILESTATES (@)

A list of file-state information for each file in the package. References the constants defined below under the heading of rpmfile_states.

RPMTAG_FILEUSERNAME (@)

A string-array data field that contains the user ID (by name) that should be used for setting ownership of the files contained in the package. There should be a one-to-one correspondance between this list and the list of files in RPMTAG_BASENAMES. See also RPMTAG_GROUPNAME.

RPMTAG_FILEVERIFYFLAGS (@)

A list of flags (implemented as a bit-field within an integer) for each file in the archive, specifying what should be checked during the verification stage. See the RPMVERIFY_* constants below.

RPMTAG_GIF ($)

Similar to RPMTAG_ICON defined below, with the restriction that the file specified should in fact be a GIF image.

RPMTAG_GROUP ($)

A one-line text string that places the package within the overall hierarchy of packages, using a UNIX-style format of denoting level with forward-slash characters (/). Most packages will have at least two elements separated by one such slash, though more are possible (as is a top-level name).

RPMTAG_ICON ($)

Specifies a file within a source-RPM (SRPM) that should be treated as an icon (of either GIF or XPM format), for potential use by GUI-based RPM tools. See RPMTAG_XPM below and RPMTAG_GIF above.

RPMTAG_INSTALLTIME ($)

The time at which the package was installed on your system. Should only be present in header objects from the database, not from uninstalled packages.

RPMTAG_INSTPREFIXES (@)

Specifies one or more prefixes that are set to the environment variables, RPM_INSTALL_PREFIX{n}, where {n} is a number starting from zero. These are set before executing any of the scripts (pre- or post-install, or verify).

RPMTAG_LICENSE ($)

The license and/or restrictions under which the package is distributed.

RPMTAG_NAME ($)

The name of the package. This is the first part of a triple used to uniquely identify a given package. It is used in conjunction with RPMTAG_VERSION and RPMTAG_RELEASE, in that order.

RPMTAG_NOPATCH (@)

RPMTAG_NOSOURCE (@)

These are used to list elements that should not be included in the resulting SRPM when it is built from a spec-file. The lists provided by the SOURCE and PATCH tags provide all elements as itemized in the spec-file. However, if either of these tags are also present, then some elements may not actually exist in the package. Both of these refer to entries in the corresponding list of names by numberical index (starting at 0).

RPMTAG_OBSOLETEFLAGS (@)

RPMTAG_OBSOLETENAME (@)

RPMTAG_OBSOLETEVERSION (@)

These three items are used in conjunction to specify packages and/or individual files which the package itself obsoletes. Of the three, only RPMTAG_OBSOLETENAME is required to have data in all elements of the array. The other two will have the same number of elements, though some (or most) may be null. This is the same approach as is used to specify the elements that the package conflicts with, those the package provides and those the package requires (see "Three-Part Linkage" below).

RPMTAG_OS ($)

The name of the O/S for which the package is intended.

RPMTAG_PACKAGER ($)

Name of the group/company/individual who built the package.

RPMTAG_PATCH (@)

A list of patch files (see patch) that will be applied to the source tree when building the package from a source-RPM (SRPM). These files are part of the bundle in the SRPM. All patch files listed in the original spec are listed here, even if some were excluded by the NOPATCH tag defined earlier.

RPMTAG_POSTIN (@)

Post-installation scripts, each entry in the list holds the text for a full script.

RPMTAG_POSTINPROG (@)

The program (and additional arguments) for executing post-installation scripts. The default is /bin/sh with no arguments. This is much like the C argv/argc pair, in that list subscript 0 represents the program itself while the remaining list items (if any) are arguments to the program.

RPMTAG_POSTUN (@)

Post-uninstallation scripts, again with one full script per array item.

RPMTAG_POSTUNPROG (@)

Specification of the program to run post-uninstallation scripts. See RPMTAG_POSTINPROG.

RPMTAG_PREFIXES (@)

The list of directory prefixes under which files are (or will be) installed. This differs from the DIRNAMES tag in that it is used to specify the parts of the filesystem affected. Thus, it is generally a shorter list and the elements are more basic (three directories under /usr in DIRNAMES will only warrant a mention of /usr in this tag).

RPMTAG_PREIN (@)

RPMTAG_PREINPROG (@)

RPMTAG_PREUN (@)

RPMTAG_PREUNPROG (@)

Specification of the scripts and commands to use in executing them, for pre-installation and pre-uninstallation. See the RPMTAG_POST* set above.

RPMTAG_PROVIDEFLAGS (@)

RPMTAG_PROVIDENAME (@)

RPMTAG_PROVIDEVERSION (@)

These three items are used in conjunction to specify the specific files that the package itself provides to other packages as possible dependancies. Of the three, only RPMTAG_PROVIDENAME is required to have data in all elements of the array. The other two will have the same number of elements, though some (or most) may be null. This three-part specification is also used to itemize dependancies and obsoletions (see "Three-Part Linkage").

RPMTAG_RELEASE ($)

The release part of the identifying triple for a package. This is combined with the RPMTAG_NAME and RPMTAG_VERSION tags to create a unique identification for each package.

RPMTAG_REQUIREFLAGS (@)

RPMTAG_REQUIRENAME (@)

RPMTAG_REQUIREVERSION (@)

These three items are used in conjunction to specify packages and/or individual files on which the package itself depends. Of the three, only RPMTAG_REQUIRENAME is required to have data in all elements of the array. The other two will have the same number of elements, though some (or most) may be null. This is the same approach as is used to specify the elements that the package provides and those the package obsoletes (see "Three-Part Linkage").

RPMTAG_RPMVERSION ($)

The version of rpm used when bundling the package.

RPMTAG_SIZE ($)

Total size of the package contents, the sum of individual file sizes.

RPMTAG_SOURCE (@)

A list of the source files that are present in the SRPM package. All files listed here will be placed in the relevant SOURCES directory when building from this SRPM. All source files listed in the original spec are listed here, even if some were excluded by the NOSOURCE tag defined earlier.

RPMTAG_SOURCERPM ($)

The source-RPM (SRPM) file used to build this package. If the file being queried is itself a source-RPM, this tag will be non-existent or null in value.

RPMTAG_SUMMARY ($)

A one line summary description of the package.

RPMTAG_TRIGGERCONDS (@)

RPMTAG_TRIGGERFLAGS (@)

RPMTAG_TRIGGERINDEX (@)

RPMTAG_TRIGGERNAME (@)

RPMTAG_TRIGGERSCRIPTPROG (@)

RPMTAG_TRIGGERSCRIPTS (@)

RPMTAG_TRIGGERVERSION (@)

These items are all taken together to manage the trigger functionality and mechanism of the RPM package. This is covered in greater depth in a later section (see "The Trigger Specifications").

RPMTAG_URL ($)

A Uniform Resource Locator (generally a WWW page) for the vendor/individual or for the software project itself.

RPMTAG_VENDOR ($)

An alternate identifier for the company that created and provided the package.

RPMTAG_VERIFYSCRIPT (@)

Scripts to be run during the verification stage. As with other script-providing tags, each array element contains one full script.

RPMTAG_VERIFYSCRIPTPROG (@)

The program (and arguments) that is to be used in executing the verification scripts. If absent or empty, /bin/sh with no arguments is used.

RPMTAG_VERSION ($)

The package version, the second part (with RPMTAG_NAME and RPMTAG_RELEASE) of the triple used to uniquely identify packages.

RPMTAG_XPM ($)

The name of a file in the SRPM that may be used as an icon by a GUI-based tool. This differs from RPMTAG_ICON above in that it implies that the file is specifically a XPM format image.

Three-Part Linkage

There are several groupings of tags that are used to specify a linkage of some sort, often external in nature. These triple-tags consist of a list of textual names, a list of corresponding versions and a list of flag fields. Of the three, only the list of names is required to have data in every element. The other two lists will have the same number of elements, however. The version values are only applied when the corresponding name refers to another RPM package.

When a version is specified, the corresponding package may need to be logically equal to, less than (older than) or greater (newer) than the version as specified. This is signified in the corresponding flags field for the triple. The flags documented later (see "Dependancy Sense Flags") can be used to determine the specific relationship.

The Trigger Specifications

The concept of trigger scripts was added into RPM from version 3.0 onwards. It provides a powerful and flexible (if delicate and tricky) mechanism by which packages may be sensitive to the installation, un-installation or upgrade of other packages. In RPM::Header terms, triggers are managed through a combination of seven different header tags.

Firstly, the tags RPMTAG_TRIGGERSCRIPTS and RPMTAG_TRIGGERSCRIPTPROG behave in the same fashion as similar tags for other script specifications. All the triggers are stored on the TRIGGERSCRIPTS tag, with each script stored as one contiguous string. The TRIGGERSCRIPTPROG array will specify the program (and optional additional arguments) if the program is anything other than /bin/sh (with no arguments).

The RPMTAG_TRIGGERNAME and RPMTAG_TRIGGERVERSION lists are used to specify the packages that a given trigger is sensitive to. The name refers to the package name (as RPM knows it to be), while the version (if specified) further narrows the dependancy. The RPMTAG_TRIGGERCONDS tag appears to be present for future use, but the RPMTAG_TRIGGERFLAGS is used as similarly- named tags are for other script specifiers. In addition to the usual relative comparison flags, these will also have some trigger-specific flags that identify the trigger as being attached to an install, un-install or upgrade. See "Dependancy Sense Flags".

Lastly, the RPMTAG_TRIGGERINDEX list is used to associate a given trigger entry (in the TRIGGERNAME list) with a particular script from the TRIGGERSCRIPTS list. This is to optimize storage, as the likelihood exists that a given script may be re-used for more than one trigger.

The tags RPMTAG_TRIGGERNAME, RPMTAG_TRIGGERVERSION, RPMTAG_TRIGGERFLAGS and RPMTAG_TRIGGERINDEX must all have the same number of elements.

Dependancy Sense Flags

The following values may be imported via the tag :rpmsense, and are used with the flags values from various triple-tag combinations, to establish the nature of the requirement relationship. In the paragraphs below, The * refers to any of REQUIRE, OBSOLETE, PROVIDE or CONFLICT. The trigger-related flags have different uses than the rest of the :rpmsense set, though they may also make use of the flags for version comparison.

RPMSENSE_SENSEMASK

This is a mask that, when applied to a value from RPMTAG_*FLAGS, masks out all bits except for the following three values:

RPMSENSE_EQUAL

RPMSENSE_GREATER

RPMSENSE_LESS

These values are used to check the corresponding entries from RPMTAG_*NAME and RPMTAG_*VERSION, and specify whether the existing file should be of a version equal to, greater than or less than the version specified. More than one flag may be present.

RPMSENSE_PREREQ

The corresponding item from RPMTAG_*NAME is a simple pre-requisite, generally without specific version checking.

RPMSENSE_TRIGGER

A mask value that will isolate the trigger flags below from any other data in the flag field.

RPMSENSE_TRIGGERIN

The corresponding trigger is an installation trigger.

RPMSENSE_TRIGGERUN

The corresponding trigger is an uninstallation trigger.

RPMSENSE_TRIGGERPOSTUN

The corresponding trigger is a post-uninstallation trigger.

Header Data Types

The following symbols may be imported via the tag :rpmtype, and represent the different types of which the various header tags (described above) may return data:

RPM_NULL_TYPE

This is used internally by the C-level rpm library.

RPM_CHAR_TYPE

This type represents single-character data.

RPM_INT8_TYPE

All items of this type are 8-bit integers.

RPM_INT16_TYPE

This type represents 16-bit integers.

RPM_INT32_TYPE

This type represents 32-bit integers.

RPM_BIN_TYPE

Data of this type represents a chunk of binary data without any further decoding or translation. It is stored as a string in Perl terms, and the length keyword should return the size of the chunk.

RPM_STRING_TYPE

RPM_STRING_ARRAY_TYPE

RPM_I18NSTRING_TYPE

These data types represent strings of text. Each are stored and treated the same internally by Perl.

Error Codes

The following symbols may be imported via the tag :rpmerr. They represent the set of pre-defined error conditions that the rpm system anticipates as possibly occuring:

RPMERR_BADARG

This is the most common error type used within the Perl RPM bindings. It is used here to indicate bad or missing data in method calls.

RPMERR_BADDEV

Signaled when a file in the contents list is a bad or unknown device type.

RPMERR_BADFILENAME

This error signifies that RPM was unable to generate a filename, or that a filename that RPM tried to use led to an error.

RPMERR_BADMAGIC

Signaled whenever an attempt to read the lead-in of the header (the "file magic" information) fails. May be due either to bad data in that part, or an I/O failure in reading the data itself.

RPMERR_BADRELOCATE

An error with the relocation specifications in the spec file.

RPMERR_BADSIGTYPE

Signals that an older, obsoleted style of signature was detected.

RPMERR_BADSPEC

General errors in the parsing or processing of the spec file.

RPMERR_CHOWN

An error occured in using the chown system call.

RPMERR_CPIO

Errors that may occur when using cpio to either package or unpack the source.

RPMERR_CREATE

This is signaled when RPM cannot create a directory or file.

RPMERR_DBCORRUPT

Signaled for consistency errors found in the database.

RPMERR_DBGETINDEX

This error represents a failure to read a requested header record from the database.

RPMERR_DBOPEN

An error when opening some component of the database.

RPMERR_DBPUTINDEX

This error signals a failure to either store or remove a specified entry into (or from) the database.

RPMERR_EXEC

An error occured when executing a sub-command (such as pgp).

RPMERR_FILECONFLICT

A file conflict (not otherwise caught or handled by rpm itself) was detected.

RPMERR_FLOCK

A failure to obtain a lock on the database. When the RPM library opens the database it places an exclusive lock on it. As such, there cannot be two processes (or two RPM::Database instances) accessing the database at one time.

RPMERR_FORK

An error occured when RPM tried to fork a child process.

RPMERR_GDBMOPEN

An error occured when trying to open a GDBM (GNU DBM) database.

RPMERR_GDBMREAD

An error occured when trying to read from a GDBM database.

RPMERR_GDBMWRITE

An error occured when trying to write to a GDBM database.

RPMERR_GZIP

An error occured with the gzip program.

RPMERR_INTERNAL

This is used to signal internal errors from within the RPM library. Odds are, if your program sees this error, you should exit as cleanly and quickly as possible.

RPMERR_LDD

An error occurred with the ldd program.

RPMERR_MKDIR

An error code was returned from the mkdir system call.

RPMERR_MTAB

An error occured when trying to determine file system information from the system mtab file.

RPMERR_NEWPACKAGE

An attempt was made to create a new package with a specification of an RPM version older (less) than 3.

RPMERR_NOCREATEDB

An attempt was made to create the database when one already exists.

RPMERR_NOGROUP

A group specified for file group-ownership was not found in the list of groups on the system. The group root will be used instead.

RPMERR_NORELOCATE

An attempt was made to relocate a package that is not relocatable.

RPMERR_NOSPACE

An attempt to write a package file failed for lack of available disk space.

RPMERR_NOSPEC

Am unpack operation on a source RPM failed to produce a spec file.

RPMERR_NOTSRPM

An operation was requested that can only be performed on a source RPM, but the specified package was a binary (or noarch) RPM.

RPMERR_NOUSER

A specified user (for file ownership) does not exist, and root will be used in its place. See RPMERR_NOGROUP.

RPMERR_OLDDB

An old-format database is present.

RPMERR_OLDDBCORRUPT

An old-format database being read (for conversion) was found to be corrupt.

RPMERR_OLDDBMISSING

A request to convert an old-format database found that there was no such database present.

RPMERR_OLDPACKAGE

An old-format package was detected.

RPMERR_PKGINSTALLED

A package requested for install is already installed on the system.

RPMERR_READ

An error occurred while reading data.

RPMERR_RENAME

An error occured while renaming a file.

RPMERR_RMDIR

An attempted removal of a directory failed.

RPMERR_RPMRC

A parsing or format error in an RC (options) file occurred.

RPMERR_SCRIPT

An error occurred while executing a script.

RPMERR_SIGGEN

Some type of error occurred when generating a signature on the package.

RPMERR_STAT

There was a failure of some sort on a stat system call.

RPMERR_UNKNOWNARCH

A requested architecture is unknown to RPM.

RPMERR_UNKNOWNOS

A requested operating system is unknown to RPM.

RPMERR_UNLINK

An error occurred with the unlink system call.

RPMERR_UNMATCHEDIF

An %else or %endif directive was seen in the spec file, for which there is no corresponding %if.

File-Verification Flags

The values in the RPMTAG_FILEVERIFYFLAGS list defined in the header-tags section earlier represent various combinations of the following values. These tags may be imported via :rpmverify.

RPMVERIFY_ALL

A full mask that will isolate the valid flag-bits from the flag field.

RPMVERIFY_NONE

An empty mask that will not match any tested verification flags.

RPMVERIFY_FILESIZE

Test the file size against the value in the header.

RPMVERIFY_GROUP

Test the file group ID against the value it should have been set to.

RPMVERIFY_LINKTO

If the file was to be a symbolic link, check that it is set correctly.

RPMVERIFY_MD5

Check the MD5 checksum for the file.

RPMVERIFY_MODE

Verify the file mode against the value it was to be set to.

RPMVERIFY_MTIME

Check the file modification-time against that which it should have been set.

RPMVERIFY_RDEV

Check the device field of the inode, if relevant.

RPMVERIFY_USER

Check the user ID to which ownership was set.

When the verification of a given file fails, the return value contains the relevant bits from the values above, corresponding to what test(s) failed. In addition, any of the following may be set to indicate a larger problem:

RPMVERIFY_LSTATFAIL

The attempt to read the inode information via lstat() was not successful. This will guarantee that other bits in the return value are set, as well.

RPMVERIFY_READFAIL

The attempt to read the file or its data (for the sake of MD5, etc.) failed.

RPMVERIFY_READLINKFAIL

An attempt to do a readlink() on the file, expected to be a symbolic link, failed.

File Specification Flags

The following tags may be imported via the :rpmfile specifier. They are used to express various characteristics of files in the archive, based on the value from RPMTAG_FILEFLAGS that corresponds to a given file.

RPMFILE_CONFIG

Not documented yet.

RPMFILE_DOC

Not documented yet.

RPMFILE_DONOTUSE

Not documented yet.

RPMFILE_GHOST

Not documented yet.

RPMFILE_LICENSE

Not documented yet.

RPMFILE_MISSINGOK

Not documented yet.

RPMFILE_NOREPLACE

Not documented yet.

RPMFILE_README

Not documented yet.

RPMFILE_SPECFILE

Not documented yet.

RPMFILE_STATE_NETSHARED

Not documented yet.

RPMFILE_STATE_NORMAL

Not documented yet.

RPMFILE_STATE_NOTINSTALLED

Not documented yet.

RPMFILE_STATE_REPLACED

Not documented yet.

Not Yet Defined

The following have not yet been categorized. They may, after further research and development, be found to be un-needed by this package.

ADD_SIGNATURE

Not documented yet.

CHECKSIG_GPG

Not documented yet.

CHECKSIG_MD5

Not documented yet.

CHECKSIG_PGP

Not documented yet.

INSTALL_HASH

Not documented yet.

INSTALL_LABEL

Not documented yet.

INSTALL_NODEPS

Not documented yet.

INSTALL_NOORDER

Not documented yet.

INSTALL_PERCENT

Not documented yet.

INSTALL_UPGRADE

Not documented yet.

QUERY_FOR_CONFIG

Not documented yet.

QUERY_FOR_DOCS

Not documented yet.

QUERY_FOR_DUMPFILES

Not documented yet.

QUERY_FOR_LIST

Not documented yet.

QUERY_FOR_STATE

Not documented yet.

RPMPROB_FILTER_DISKSPACE

Not documented yet.

RPMPROB_FILTER_FORCERELOCATE

Not documented yet.

RPMPROB_FILTER_IGNOREARCH

Not documented yet.

RPMPROB_FILTER_IGNOREOS

Not documented yet.

RPMPROB_FILTER_OLDPACKAGE

Not documented yet.

RPMPROB_FILTER_REPLACENEWFILES

Not documented yet.

RPMPROB_FILTER_REPLACEOLDFILES

Not documented yet.

RPMPROB_FILTER_REPLACEPKG

Not documented yet.

RPMSIGTAG_GPG

Not documented yet.

RPMSIGTAG_LEMD5_1

Not documented yet.

RPMSIGTAG_LEMD5_2

Not documented yet.

RPMSIGTAG_MD5

Not documented yet.

RPMSIGTAG_PGP

Not documented yet.

RPMSIGTAG_PGP5

Not documented yet.

RPMSIGTAG_SIZE

Not documented yet.

RPMSIG_BAD

Not documented yet.

RPMSIG_NOKEY

Not documented yet.

RPMSIG_NOTTRUSTED

Not documented yet.

RPMSIG_OK

Not documented yet.

RPMSIG_UNKNOWN

Not documented yet.

RPMTRANS_FLAG_ALLFILES

Not documented yet.

RPMTRANS_FLAG_BUILD_PROBS

Not documented yet.

RPMTRANS_FLAG_JUSTDB

Not documented yet.

RPMTRANS_FLAG_KEEPOBSOLETE

Not documented yet.

RPMTRANS_FLAG_NODOCS

Not documented yet.

RPMTRANS_FLAG_NOSCRIPTS

Not documented yet.

RPMTRANS_FLAG_NOTRIGGERS

Not documented yet.

RPMTRANS_FLAG_TEST

Not documented yet.

UNINSTALL_ALLMATCHES

Not documented yet.

UNINSTALL_NODEPS

Not documented yet.

VERIFY_DEPS

Not documented yet.

VERIFY_FILES

Not documented yet.

VERIFY_MD5

Not documented yet.

VERIFY_SCRIPT

Not documented yet.

SEE ALSO

RPM, perl, rpm

AUTHORS

Randy J. Ray <rjray@blackperl.com>, Alexey Tourbin <at@altlinux.org>.

cpanm RPM

perl -MCPAN -e shell
install RPM