ELDKIndividualPackages < DULG

%SECTION0{name=ELDKIndividualPackages}% Installation and Removal of Individual Packages

The ELDK has an RPM-based structure. This means that on the ISO
image, individual components of the ELDK are in the form of RPM
packages, and after installation, the ELDK maintains its own database
which contains information about installed packages. The RPM database
is kept local to the specific ELDK installation, which allows you to
have multiple independent ELDK installations on your host system.
(That is, you can install several instances of ELDK under different
directories and work with them independently). Also, this provides
for easy installation and management of individual ELDK packages.
                                                                                
To list the installed ELDK RPM packages, use the following command:
                                                                                
<verbatim>
bash$ ${CROSS_COMPILE}rpm -qa
</verbatim>

To remove an ELDK package, use the following command:
                                                                                
<verbatim>
bash$ ${CROSS_COMPILE}rpm -e <package_name>
</verbatim>
                                                                                
To install a package, use the following command:
                                                                                
<verbatim>
bash$ ${CROSS_COMPILE}rpm -i <package_file_name>
</verbatim>
                                                                                
To update a package, use the following command:
                                                                                
<verbatim>
bash$ ${CROSS_COMPILE}rpm -U <package_file_name>
</verbatim>

For the above commands to work correctly, it is crucial that the
correct =rpm= binary gets invoked. In case of
multiple ELDK installations and !RedHat-based host system, there may
well be several =rpm= tools installed on the host
system.
                                                                                
You must make sure, either by using an explicit path or by having set
an appropriate =PATH= environment variable, that
when you invoke =rpm= to install/remove components
of a ELDK installation, it is the ELDK's =rpm=
utility that gets actually invoked. The =rpm=
utility is located in the =bin= subdirectory
relative to the ELDK root installation directory.
                                                                                
To avoid confusion with the host OS (!RedHat) =rpm=
utility, the ELDK creates symlinks to its =rpm=
binary with the names such that it could be invoked using the
=${CROSS_COMPILE}rpm= notation, for all supported
[[ELDKUsage#Table_CrossCompile][$CROSS_COMPILE]] values.

%T% The standard (host OS) =rpm= utility allows various
macros and configuration parameters to specified in
user-specific _~/.rpmrc_ and _~/.rpmmacros_ files. The ELDK
rpm tool also has this capability, but the names
of the user-specific configuration files
are _~/.eldk_rpmrc_ and _~/.eldk_rpmmacros_, respectively.
3.5.3. Initial Installation		1. Abstract		3.5.5. Removal of the Entire Installation
Prev		Home		Next