Edit rpm cheat sheet

Title:

Last edited: 5:34:09 pm on 18 May 2010 by salchicha.sico.local

! One-liners

NOTA: *Sitio con todas las respuestas que no están aquí>http://fedoranews.org/alex/tutorial/rpm/*.
NOTA2: Hay un artículo muy completo en:
=salchicha:/home/dario/Programacion/doc/rpm/l-rpm3.pdf
NOTA3: *Learn Linux, 101: RPM and YUM package management>http://www.ibm.com/developerworks/linux/library/l-lpic1-v3-102-5/index.html?ca=dgr-lnxw03RPM-YUMdth-LX*.

!Instalar un paquete
<tt>rpm -i nombre.rpm</tt>

!Desinstalar un paquete
<tt>rpm -e nombre</tt>

!Comprobar si un paquete está instalado
<tt>rpm -qa | grep nombrepaquete</tt>

!Ver la información de un paquete ya instalado
<tt>rpm -qi nombrepaquete</tt>

!Ver la información de un paquete antes de instalarlo
<tt>rpm -qip nombrepaquete.rpm</tt>

!Ver el changelog de un paquete antes de instalarlo
<tt>rpm -qp nombrepaquete.rpm --changelog</tt>

!Extraer un sólo archivo del rpm
<tt>rpm2cpio packageXyz.rpm | cpio -imvd ./usr/packageXyz/randomfile</tt>

! Generar RPMs en el home del usuario

Requisitos previos:
- Crear los directorios BUILD RPMS SOURCES SPECS SRPMS en /home/metro
- Crear un fichero "$HOME/.rpmmacros" con el contenido "%_topdir        /home/metro"

Preparar la script para generar el tar.gz y el spec:
# Se instala todo en la máquina a mano
# En el directorio SOURCES se pone una script que empaquete "lo que se ha metido a mano", p. ej. <br><table border=1><tr><td><tt>#!/bin/sh<br>nombre="isacd"<br>directorios="/home/metro/isacd"<br>rm -f sico-${nombre}-op-1.0a.tar.gz<br>tar czvf sico-${nombre}-op-1.0a.tar.gz ${directorios} > ./${nombre}.txt<br>(cat ../SPECS/sico-${nombre}-op.spec | tr "<br>" "@" | sed "s/$%defattr(-,root,root)@$.*/\1/g" | tr "@" "<br>" ; cat ./${nombre}.txt ) > ../SPECS/sico-${nombre}-op.spec.new<br>mv ../SPECS/sico-${nombre}-op.spec.new</tt></td></tr></table>
# En el directorio SPECS se pone una spec con lo que tiene que hacer:<br><table border=1><tr><td><tt>%define name sico-isacd-op<br>%define version 1.0<br>%define release 1.%(date +"%Y%m%d%H%M")<br><br>Summary: Ficheros necesarios en un puesto de operador para el isa/isacd/isatce<br>Name: %{name}<br>Version: %{version}<br>Release: %{release}<br>Source: %{name}-%{version}a.tar.gz<br>License: Other/Propietary<br>Group: System/Base<br>Buildroot: %{_builddir}/%{name}-root<br>%description<br>Este fichero incluye los ficheros instalables en /home/metro/isacd<br>%prep<br>rm -rf $RPM_BUILD_ROOT<br>%build<br>echo Nothing to build<br>%install<br>mkdir -p $RPM_BUILD_ROOT<br>cd $RPM_BUILD_ROOT && tar -xzpf /home/metro/SOURCES/%{name}-%{version}a.tar.gz<br>%clean<br>rm -rf $RPM_BUILD_ROOT<br>%files<br>%defattr(-,root,root)</tt></td></tr></table>

Generar el rpm usando la script y el spec anterior:
# Te vas a /home/metro/SOURCES y ejecutas el "./gen-xxx" correspondiente
# Te vas a /home/metro/SPECS y haces el "rpmbuild -ba nombrespec.spec"
# Buscas el resultado en /home/metro/RPMS/i386

_
! Información de *http://www.han.de/~racke/rpm.html*
NOTA: Hay que hacer *malabarismos para poner las variables>http://www.redhat.com/archives/rpm-list/2000-August/msg00297.html*: se ponen en el .rpmmacros y con %_ delante y un espacio detrás (p.ej. "%_topdir        /u02/RPMBuild")
_
<html>
<H1>Piled RPM Remarks</H1>
<A NAME="0"></A>
<UL>
<LI><A HREF="#37">Concepts</A>
<UL>
<LI><A HREF="#45">Dependencies</A>
</UL>
<LI><A HREF="#66">Querying Packages</A>
<UL>
<LI><A HREF="#70">List Packages</A>
</UL>
<LI><A HREF="#85">Configuration</A>
<UL>
<LI><A HREF="#93">Architecture and Operating System</A>
<LI><A HREF="#103">Directories</A>
<LI><A HREF="#180">Building</A>
</UL>
<LI><A HREF="#194">Building Packages</A>
<UL>
<LI><A HREF="#207">Dependencies</A>
<LI><A HREF="#239">Environment Variables</A>
<LI><A HREF="#buildscripts">Build Scripts</A>
<UL>
<LI><A HREF="#342">The %prep script</A>
</UL>
<LI><A HREF="#372">The File List</A>
<UL>
<LI><A HREF="#379">Directives</A>
<UL>
<LI><A HREF="#387">The %doc Directive</A>
<LI><A HREF="#404">The %ghost Directive</A>
</UL>
<LI><A HREF="#421">Dynamically Build File Lists</A>
</UL>
<LI><A HREF="#431">Other tags</A>
<UL>
<LI><A HREF="#435">Obsoletes</A>
</UL>
<LI><A HREF="#443">Macros and variables</A>
</UL>
<LI><A HREF="#459">Variables</A>
<LI><A HREF="#489">The RPM Library API</A>
<UL>
<LI><A HREF="#497">Status Codes</A>
</UL>
<LI><A HREF="#510">Index of Files and Directories</A>
<LI><A HREF="#515">Index of Tags, Macros, Variables and Sections</A>
<LI><A HREF="#520">Concept Index</A>
</UL>

<H2><A NAME="37">Concepts</A></H2>

<H3><A NAME="45">Dependencies</A></H3>
Most packages can not work standalone, other packages are needed for proper
usage. We say, a package <DFN>depends</DFN> on another one or <DFN>requires
</DFN> it. These dependencies must satisfied at installation time. For
example, package <VAR>foo</VAR> requires <VAR>bar</VAR>. So <VAR>foo</VAR>
must be installed after package <VAR>bar</VAR> or at least simultaneously.

<H2><A NAME="66">Querying Packages</A></H2>

<H3><A NAME="70">List Packages</A></H3>
<CODE>rpm -qa</CODE> prints the installed packages on stdout, unfortunately
unsorted. Just pass the output of <CODE>rpm</CODE> to <CODE>sort</CODE> for a
convenient list: <PRE>
rpmuser % rpm -qa | sort | tail -n5
vrfy-961113-3
w3-3.0.86-1
wwwoffle-1.2-1
zlib-1.0.4-1
zlib-devel-1.0.4-1
</PRE>

<H2><A NAME="85">Configuration</A></H2>

<H3><A NAME="93">Architecture and Operating System</A></H3>
These configuration variables define the architecture and operating system
that RPM is running on resp. is building for.

<H3><A NAME="103">Directories</A></H3>
<DL>
<DT>topdir<DD>Top level directory for <CODE>builddir</CODE>, <CODE>rpmdir
</CODE>, <CODE>sourcedir</CODE>, <CODE>specdir</CODE> and <CODE>srcrpmdir
</CODE><A NAME="124">.</A><DT>builddir<DD><A NAME="130">Directory in which RPM will build packages.</A><DT>rpmdir<DD><A NAME="136">Directory in which RPM will store binary packages.</A><DT><A NAME="140">sourcedir</A><DD><A NAME="150"> 	Directory in which RPM will look for sources and patches.</A>
<DT>specdir<DD><A NAME="156">Directory in which RPM will look for spec files.</A><DT><A NAME="160">defaultdocdir</A><DD> Directory which RPM
will use as root directory for documentation files as specified by the 
<CODE><A HREF="#docdirective">%doc</A></CODE><A NAME="167"> directive. 	Default is </A><CODE>/usr/doc</CODE>.
</DL>

<H3><A NAME="180">Building</A></H3>
<DL>
<DT><A NAME="184">optflags</A><DD> Standard set of options for compilation.
</DL>

<H2><A NAME="194">Building Packages</A></H2>
<A NAME="198">Each </A><DFN>spec file</DFN> defines parameters and instructions for building one or
more RPM packages.

<H3><A NAME="207">Dependencies</A></H3>
<A NAME="211">Dependencies between packages are specified with the </A><CODE>Requires</CODE><A NAME="215"> and </A><CODE>Provides</CODE> tags:<PRE>
	Requires: foo
	Requires: bar = 1.2.3
</PRE>Other operators
for version comparison are: <CODE>&lt;</CODE>, <CODE>&gt;</CODE>, <CODE>&gt;=
</CODE> and <CODE>&lt;=</CODE>.

<H3><A NAME="239">Environment Variables</A></H3>
<A NAME="243">The following </A> environment variables are set before executing any of the <A HREF="#buildscripts">build scripts</A><A NAME="257">: </A>
<DL>
<DT><CODE><A NAME="263">RPM_ARCH</A></CODE><DD><DT><CODE><A
NAME="269">RPM_BUILD_DIR</A></CODE><DD><DT><CODE><A
NAME="275">RPM_BUILD_ROOT</A></CODE><DD><DT><CODE><A
NAME="281">RPM_DOC_DIR</A></CODE><DD><DT><CODE><A
NAME="287">RPM_OPT_FLAGS</A></CODE><DD><DT><CODE><A NAME="293">RPM_OS</A>
</CODE><DD><DT><CODE><A NAME="299">RPM_PACKAGE_NAME</A></CODE><DD><DT>
<CODE><A NAME="305">RPM_PACKAGE_RELEASE</A></CODE><DD><DT><CODE><A
NAME="311">RPM_PACKAGE_VERSION</A></CODE><DD><DT><CODE><A
NAME="317">RPM_ROOT_DIR</A></CODE><DD><DT><CODE>RPM_SOURCE_DIR</CODE><DD>
Directory in which RPM will look for sources and patches.
</DL>

<H3><A NAME="buildscripts">Build Scripts</A></H3>

<H4><A NAME="342">The <CODE>%prep</CODE> script</A></H4>
<A NAME="344">Unpacks the </A>source archives<A NAME="350"> into the build directory and applies </A>patches:<PRE>%prep
%setup
</PRE>After unpacking RPM changes to the main
source directory, e.g. <CODE>rpm-2.5.2</CODE>. The <CODE>-n</CODE><A NAME="362"> switch of the </A><CODE>
%setup</CODE> tag allows you to explicitly specify a directory:<PRE>%prep
%setup -n cgi.tcl-0.7
</PRE>

<H3><A NAME="372">The File List</A></H3>
The package we are building will contain all files appearing in the file
list: <PRE>%files
%defattr(-,root,root)
/usr/bin/foo
/usr/lib/libfoo.a
/usr/include/foo.h
</PRE>

<H4><A NAME="379">Directives</A></H4>

<H5><A NAME="387">The <CODE>%doc</CODE> Directive</A></H5>
The <CODE><A  NAME="docdirective">%doc</A></CODE> directive instructs RPM to copy the specified files
into the documentation directory. The <CODE>-P</CODE> flag is useful to
preserve the directory structure.

<H5><A NAME="404">The <CODE>%ghost</CODE> Directive</A></H5>
The <CODE>%ghost</CODE><A NAME="411"> directive instructs RPM not to install the specified file(s). They will be owned by that package and removed if they exists when the package is removed.  This can be useful for things like </A>log files<A NAME="414"> and </A>state files.

<H4><A NAME="421">Dynamically Build File Lists</A></H4>
With the <CODE>-f</CODE> option RPM can be instructed to read the file names
from a file generated during package building: <PRE>%files -f MANIFEST</PRE>

<H3><A NAME="431">Other tags</A></H3>

<H4><A NAME="435"><CODE>Obsoletes</CODE></A></H4>
Declares which packages are obsoleted by this one. Older versions of the
package are automatically obsoleted.

<H3><A NAME="443">Macros and variables</A></H3>
<A NAME="449">RPM defines the following environment variables:</A><DL>
<DT><CODE>RPM_INSTALL_PREFIX</CODE><DD>value of the <CODE>Prefix:</CODE>
tag
</DL>

<H2><A NAME="459">Variables</A></H2>
<DL>
<DT><CODE>builddir</CODE><DD>Directory in which RPM will build packages.
<DT><CODE>optflags</CODE><DD>Standard set of options for compilation.<DT>
<CODE>rpmdir</CODE><DD>Directory in which RPM will store binary packages.
<DT><CODE>sourcedir</CODE><DD>Directory in which RPM will look for sources
and patches.<DT><CODE>specdir</CODE><DD>Directory in which RPM will look for
spec files.
</DL>

<H2><A NAME="489">The RPM Library API</A></H2>

<H3><A NAME="497">Status Codes</A></H3>
<A NAME="499">The error </A>status codes are defined in <CODE>rpmlib.h</CODE>.

<H2><A NAME="510">Index of Files and Directories</A></H2>
<UL>
<LI><A HREF="#167">/usr/doc</A>
</LI>
</UL>

<H2><A NAME="515">Index of Tags, Macros, Variables and Sections</A></H2>
<UL>
<LI><A HREF="#383">%doc</A>
</LI>
<LI><A HREF="#400">%ghost</A>
</LI>
<LI><A HREF="#333">%prep</A>
</LI>
<LI><A HREF="#362">%setup</A>
</LI>
<LI><A HREF="#124">builddir</A>
</LI>
<LI><A HREF="#156">defaultdocdir</A>
</LI>
<LI><A HREF="#435">Obsoletes</A>
</LI>
<LI><A HREF="#180">optflags</A>
</LI>
<LI><A HREF="#215">Provides</A>
</LI>
<LI><A HREF="#211">Requires</A>
</LI>
<LI><A HREF="#257">RPM_ARCH</A>
</LI>
<LI><A HREF="#263">RPM_BUILD_DIR</A>
</LI>
<LI><A HREF="#269">RPM_BUILD_ROOT</A>
</LI>
<LI><A HREF="#275">RPM_DOC_DIR</A>
</LI>
<LI><A HREF="#449">RPM_INSTALL_PREFIX</A>
</LI>
<LI><A HREF="#281">RPM_OPT_FLAGS</A>
</LI>
<LI><A HREF="#287">RPM_OS</A>
</LI>
<LI><A HREF="#293">RPM_PACKAGE_NAME</A>
</LI>
<LI><A HREF="#299">RPM_PACKAGE_RELEASE</A>
</LI>
<LI><A HREF="#305">RPM_PACKAGE_VERSION</A>
</LI>
<LI><A HREF="#311">RPM_ROOT_DIR</A>
</LI>
<LI><A HREF="#317">RPM_SOURCE_DIR</A>
</LI>
<LI><A HREF="#130">rpmdir</A>
</LI>
<LI><A HREF="#136">sourcedir</A>
</LI>
<LI><A HREF="#150">specdir</A>
</LI>
<LI><A HREF="#103">topdir</A>
</LI>
</UL>

<H2><A NAME="520">Concept Index</A></H2>
<UL>
<LI><A HREF="#93">architecture</A>
</LI>
<LI><A HREF="#buildscripts">build scripts</A>
</LI>
<LI>compilation
<UL>
<LI><A HREF="#184">options</A>
</LI>
</UL>
</LI>
<LI><A HREF="#45">dependencies</A>
</LI>
<LI>documentation files
<UL>
<LI><A HREF="#160">root directory</A>
</LI>
</UL>
</LI>
<LI><A HREF="#243">environment variables</A>
</LI>
<LI><A HREF="#497">error codes</A>
</LI>
<LI><A HREF="#411">log files</A>
</LI>
<LI><A HREF="#93">operating system</A>
</LI>
<LI>options
<UL>
<LI><A HREF="#184">compilation</A>
</LI>
</UL>
</LI>
<LI><A HREF="#140">patches</A>
<UL>
<LI><A HREF="#140">directory</A>
</LI>
</UL>
</LI>
<LI><A HREF="#buildscripts">scripts</A>
</LI>
<LI>source
<UL>
<LI><A HREF="#344">archives</A>
</LI>
</UL>
</LI>
<LI>sources
<UL>
<LI><A HREF="#140">directory</A>
</LI>
</UL>
</LI>
<LI>spec
<UL>
<LI><A HREF="#198">file</A>
</LI>
</UL>
</LI>
<LI><A HREF="#414">state files</A>
</LI>
<LI>status
<UL>
<LI><A HREF="#499">codes</A>
</LI>
</UL>
</LI>
<LI><A HREF="#342">unpack</A>
</LI>
<LI>variables
<UL>
<LI><A HREF="#243">environment</A>
</LI>
</UL>
</LI>
</UL>

<HR><ADDRESS>
Written by Stefan Hornburg <A HREF="mailto:racke@gundel.han.de">&lt;racke@gundel.han.de&gt;</A><BR>Translated from <A href="rpm.tcl">rpm.tcl</A> by <A	HREF="http://www.han.de/~racke/InfoPrism/">Info Prism's sgml2html</A> v0.0.6 <BR>Last modified 12 January 1999</ADDRESS><HR>

</html>
_
! Información obtenida de *http://www.justlinux.com/nhf/Distribution_Specific/Red_Hat_Linux*
_
<html>
<h2><font color="#9E0D08">Help File Library:</font> Red Hat RPM Guide</h2>
                          <p>In general, normal usage of the rpm command can be 
                            summarised as follows: <br>
                            <br>
                            <h3>Installation/Upgrading/Removal</h3>
<p>To install a package type: 
                            <font color="#0000FF">rpm -ivh</font><br>
                            ex. <font color="#FF0000">rpm -ivh somepackage.1.1-4.i386.rpm</font> 
                          </p>
                          <p>To upgrade a package: <font color="#0000FF">rpm -Uvh 
                            [filename]</font> <br>
                            ex. <font color="#FF0000">rpm -Uvh somepackage.1.1-5.i386.rpm</font><br>
                          </p>
                          <p>To remove a package: <font color="#0000FF">rpm -e 
                            [packagename]</font> <br>
                            ex. <font color="#FF0000">rpm -evh somepackage</font> 
                          </p>
                          <p>Also for upgrading or installing some packages you 
                            may need to use additional flags to force the install 
                            happen. It is only recommended to use these if you 
                            know why these flags were needed. <font color="#0000FF">--force</font> 
                            will overwrite files that are owned by other packages. 
                            <font color="#0000FF">--nodeps</font> will install 
                            even if the package needs packages that were not installed. 
                          </p>
                          <p> To see if a package is installed: <font color="#0000FF">rpm 
                            -q [packagename]</font> <br>
                            ex. <font color="#FF0000">rpm -q somepackage</font> 
                          </p>
                          <p>To get info on an installed package: <font color="#0000FF">rpm 
                            -qi [packagename]</font> <br>
                            ex. <font color="#FF0000">rpm -qi somepackage</font> 
                          </p>
                          <p>To list which files belong to a package: rpm -ql 
                            [packagename] <br>
                            ex. <font color="#FF0000">rpm -ql somepackage</font> 
                          </p>
                          <p>To see what package a file belongs to: <font color="#0000FF">rpm 
                            -qf</font> <br>
                            ex. <font color="#FF0000">rpm -qf /usr/bin/some_executable</font></p>
                          <p>One can usually join various query commands together, 
                            so <font color="#0000FF">rpm -qil</font> will give 
                            info and list all the files in the package. </p>
                          <p>To look in a rpm filename that isnt installed, you 
                            tag on the p to the query line. <br>
                            ex. <font color="#FF0000">rpm -qilp somepackage.1.1-4.i386.rpm</font> 
                            will list the information and the files contained 
                            in somepackage. </p>
                          <p>--More Advanced usages can be found in the <font color="#0000FF">man</font> 
                            page for rpm and at the web site: <a href="ftp://ftp.rpm.org">ftp.rpm.org</a> 
                          </p>
                          <p>--Verification To see what files on the system may 
                            have changed from their initial settings you can use 
                            RPM, to check up on them. <font color="#FF0000">rpm 
                            -Va</font> will give you a list of all files that 
                            have changed in one form or another since the package 
                            it is associated was installed. This can be a lot 
                            of files (and a lot may be changed due to post installation 
                            work). </p>
                          <p>To just see what packages have changed so that you 
                            can verify them more individually, you can do the 
                            following: <br>
                            <font color="#FF0000">rpm -Va | awk '{print $2}' | 
                            xargs rpm -qf | sort -u &amp;&gt; /tmp/file1</font> 
                            <br>
                            <br>
                            Then look in the file <font color="#FF0000">/tmp/file1</font> 
                            for which packages have had changes from them. </p>

</html>
_
! Generar paquetes RPM

Ver los siguientes documentos:
- *howto sencillo de generación de paquetes RPM>http://erizo.ucdavis.edu/~dmk/notes/RPMs/Creating_RPMs.html*
- *howto oficial>http://www.rpm.org/RPM-HOWTO/build.html*
- *scripts de los rpms: %pre, %post, etc>http://www.rpm.org/max-rpm/s1-rpm-inside-scripts.html*
- *por qué no se pueden hacer preguntas al instalar los rpms>http://www.rpm.org/hintskinks/interactive/* (básicamente: ya que no tienen un equivalente al debconf de debian, la única manera de posibilitar hacer instalaciones desatendidas es que no haya preguntas -- lo del "DEBIAN_FRONTEND=noninteractive dpkg -i nombre.deb" no tiene equivalente en redhat)
Hay disponible *mucha más información>http://www.google.es/search?hl=es&ie=ISO-8859-1&q=rpm+spec+howto&meta= sobre el tema.

- lock this page
- enter new password
- reenter same password

Send e-mail alerts to these addresses upon next save: