From 3132d1505c90545de7b1fed16b4dd7ccd7091fd2 Mon Sep 17 00:00:00 2001 From: Ioana Valentina Nicolaescu Date: Wed, 9 Oct 2019 13:13:07 +0200 Subject: Update package management section from deb to rpm Change-Id: Icfc821b3efd036baedd0975f5ef227c4596200e7 Signed-off-by: Ioana Valentina Nicolaescu --- .../doc/application_development.xml | 10 +- .../doc/getting_enea_linux.xml | 4 +- .../doc/using_enea_linux.xml | 116 ++++++++++++--------- 3 files changed, 71 insertions(+), 59 deletions(-) diff --git a/doc/book-enea-linux-user-guide/doc/application_development.xml b/doc/book-enea-linux-user-guide/doc/application_development.xml index 0e2edf4..a94c422 100644 --- a/doc/book-enea-linux-user-guide/doc/application_development.xml +++ b/doc/book-enea-linux-user-guide/doc/application_development.xml @@ -156,7 +156,7 @@ MODULE_LICENSE("GPL"); This example will show how to generate a recipe from the existing application code and Makefile, edit the recipe in order to provide an installation path for the application, build the recipe, and deploy the - output on a target, or create a DEB package from the recipe and install + output on a target, or create a RPM package from the recipe and install the package. @@ -266,16 +266,16 @@ Parsing recipes..done. NOTE: Successfully deployed <SDK_dir>/tmp/work/<arch>-enea-linux/my-hello-recipe/1.0-r0/image - As an alternative you can create a DEB package: + As an alternative you can create a RPM package: $ devtool package my-hello-recipe ... NOTE: Your packages are in <SDK_dir>/tmp/deploy/deb - Then copy the DEB package on the target and install it using - dpkg: + Then copy the RPM package on the target and install it using + rpm: - # dpkg -i my-hello-recipe-1.0-r0.1.<arch>.deb + # rpm -i my-hello-recipe-1.0-r0.1.<arch>.rpm diff --git a/doc/book-enea-linux-user-guide/doc/getting_enea_linux.xml b/doc/book-enea-linux-user-guide/doc/getting_enea_linux.xml index 21d0cb9..b747b2e 100644 --- a/doc/book-enea-linux-user-guide/doc/getting_enea_linux.xml +++ b/doc/book-enea-linux-user-guide/doc/getting_enea_linux.xml @@ -39,8 +39,8 @@ - deb directory - this directory contains all - the packages included in the distribution in deb format, which can be + rpm directory - this directory contains all + the packages included in the distribution in rpm format, which can be installed using the package manager. diff --git a/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml b/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml index a68f7da..a6a0ed6 100644 --- a/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml +++ b/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml @@ -702,31 +702,31 @@ $ devtool runqemu kvm enea-image-standard nographic slirp image in a consistent way, e.g. to install, upgrade, or delete packages considering the dependencies. The package management systems supported by Enea Linux are described in this section. More information about PMS can - be found in the Yocto 2.5 document Yocto + be found in the Yocto 2.7 document Yocto Project Mega Manual. If needed replace the Yocto version in the link. -
- APT Package Management (DEB Packages) +
+ RPM Package Management (RPM Packages) - Enea Linux provides DEB packages on Enea Linux provides RPM packages on linux.enea.com site, in directory - <release>/<target>/deb/. + <release>/<target>/rpm/. +--> + The application for performing runtime package management of RPM + packages on the target is called rpm. - The application for performing runtime package management of DEB - packages on the target is called apt-get. - - Use the apt-get command to install, upgrade, or - remove packages. Before using any apt-get options that require network + Use the rpm command to install, upgrade, or + remove packages. Before using any rpm options that require network access, please check that the network is configured and working properly. - The apt-get command is by default included in + The rpm command is by default included in Enea Linux images. -
+ + +
+ Preparation + + RPM packages need to first be downloaded on target. + # wget https://rpmfind.net/linux/fedora/linux/development/rawhide/Everything/ +aarch64/os/Packages/v/vim-common-8.1.2120-1.fc32.aarch64.rpm + They can be copied either from public maintained repositories or from locally maintained collections of useful RPMs. + # wget http://linux.enea.com/RPM/aarch64/vim-common-7.4.481-r0.0.aarch64.rpm + + + + RPM is also identifying and checking for package dependencies. It warns if the package can not be installed correctly and lists what needs to be done. + +
-
+
Installing - - DEB packages typically have file names like - foo-1.0.1-r0.0_arm64.deb The file name includes the package name + + RPM packages typically have file names like + foo-1.0.1-r0.0_arm64.rpm The file name includes the package name (foo), version (1.0.1), revison (r0.0), and architecture (arm64). To install a package, log in as root and type the following command at a shell prompt: - # apt-get install foo + # rpm -i vim-common-8.1.1017-r0.0.aarch64.rpm +user.notice [RPM][351]: Transaction ID 5d836e00 started +user.notice [RPM][351]: install vim-common-8.1.1017-r0.0.aarch64: success +user.notice [RPM][351]: install vim-common-8.1.1017-r0.0.aarch64: success +user.notice [RPM][351]: Transaction ID 5d836e00 finished: 0 - The apt-get install command will install one - or more packages in the system.
-
+
Upgrading - The apt-get upgrade command will upgrade one - or more packages which are currently installed in the system. If no - packages are given, all installed packages will be checked. - - # apt-get upgrade foo + The rpm -U command will upgrade one + or more packages which are currently installed in the system. + + + # rpm -U vim-common-8.1.1518-r0.0.aarch64.rpm +user.notice [RPM][346]: Transaction ID 5d836d54 started +user.notice [RPM][346]: erase vim-common-8.1.1017-r0.0.aarch64: success +user.notice [RPM][346]: install vim-common-8.1.1518-r0.0.aarch64: success +user.notice [RPM][346]: erase vim-common-8.1.1017-r0.0.aarch64: success +user.notice [RPM][346]: install vim-common-8.1.1518-r0.0.aarch64: success +user.notice [RPM][346]: Transaction ID 5d836d54 finished: 0
-
+
Removing - The apt-get remove command will remove one or - more packages which are currently installed in the system. + The rpm -e command will remove the + package which is currently installed in the system. Example: - # apt-get remove ptest-runner -Reading package lists... Done -Building dependency tree -Reading state information... Done -The following packages were automatically installed and are no longer required: - libc6-dbg libc6-dev libc6-extra-nss libc6-thread-db libcidn1 - linux-libc-headers-dev -Use 'apt autoremove' to remove them. -The following packages will be REMOVED: - ptest-runner -0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. -After this operation, 0 B of additional disk space will be used. -Do you want to continue? [Y/n] y -(Reading database ... 5766 files and directories currently installed.) -Removing ptest-runner (2.0.2+git0+6d2872116c-r0.0) ... + # rpm -e vim-common +user.notice [RPM][350]: Transaction ID 5d836dc9 started +user.notice [RPM][350]: erase vim-common-8.1.1518-r0.0.aarch64: success +user.notice [RPM][350]: erase vim-common-8.1.1518-r0.0.aarch64: success +user.notice [RPM][350]: Transaction ID 5d836dc9 finished: 0
-
+
Searching - The apt-cache search allows searching for the + The rpm -q allows searching for the given expressions in the name, summary and description of known packages. Example: - # apt-cache search ptest-runner -ptest-runner - A C program to run all installed ptests -ptest-runner-dbg - A C program to run all installed ptests - Debugging files -ptest-runner-dev - A C program to run all installed ptests - Development files + # rpm -q vim-common +vim-common-8.1.1017-r0.0.aarch64
-- cgit v1.2.3-54-g00ecf