From 1a4c0bfafdbd607606587752eec57641a9a4c9f1 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 27 Mar 2017 12:47:57 -0700 Subject: dev-manual; ref-manual: Updates to replace "smart" with "dnf" Fixes [YOCTO #9675] Various fixes to replace the "smart" package manager references with "dnf". (From yocto-docs rev: 721dc7fb637c4c03534eb19f61b0b08a7303826d) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../dev-manual/dev-manual-common-tasks.xml | 47 +++++++++++++--------- 1 file changed, 27 insertions(+), 20 deletions(-) (limited to 'documentation/dev-manual') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 9174417ae9..0f6b32209f 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -8244,13 +8244,14 @@ Using RPM - The smart application performs + The dnf application performs runtime package management of RPM packages. You must perform an initial setup for - smart on the target machine + dnf on the target machine if the PACKAGE_FEED_ARCHS, - PACKAGE_FEED_BASE_PATHS, and + PACKAGE_FEED_BASE_PATHS, + and PACKAGE_FEED_URIS variables have not been set or the target image was built before the variables were set. @@ -8262,21 +8263,26 @@ all, i586, and qemux86 from a server named my.server. - You must inform smart of the - availability of these databases by issuing the - following commands on the target: + You must inform dnf of the + availability of these databases by creating a + /etc/yum.repos.d/oe-packages.repo + file with the following content: - # smart channel --add i585 type=rpm-md baseurl=http://my.server/rpm/i586 - # smart channel --add qemux86 type=rpm-md baseurl=http://my.server/rpm/qemux86 - # smart channel --add all type=rpm-md baseurl=http://my.server/rpm/all + [oe-packages] + baseurl="http://my.server/rpm/i586 http://my.server/rpm/qemux86 http://my.server/rpm/all" From the target machine, fetch the repository: - # smart update + # dnf makecache - After everything is set up, smart + After everything is set up, dnf is able to find, install, and upgrade packages from the specified repository. + + See the + Dnf documentation + for additional information. + @@ -8446,11 +8452,11 @@ In addition to being able to sign RPM packages, you can also enable the OpenEmbedded build system to be able to - handle previously signed package feeds for both RPM and IPK + handle previously signed package feeds for IPK packages. The OpenEmbedded build system does not currently - support signed DPKG package feeds. + support signed DPKG or RPM package feeds. The steps you need to take to enable signed package feed use are similar to the steps used to sign RPM packages. @@ -9321,12 +9327,13 @@ Be sure your host's firewall accepts incoming connections from 192.168.7.0/24: - Some of the tests (in particular smart tests) start an - HTTP server on a random high number port, which is - used to serve files to the target. + Some of the tests (in particular dnf tests) start + an HTTP server on a random high number port, + which is used to serve files to the target. The smart module serves - ${DEPLOY_DIR}/rpm so it can run - smart channel commands. That means your host's firewall + ${WORKDIR}/oe-rootfs-repo + so it can run dnf channel commands. + That means your host's firewall must accept incoming connections from 192.168.7.0/24, which is the default IP range used for tap devices by runqemu. @@ -9826,7 +9833,7 @@ The default tests for the image are defined as: - DEFAULT_TEST_SUITES_pn-image = "ping ssh df connman syslog xorg scp vnc date rpm smart dmesg" + DEFAULT_TEST_SUITES_pn-image = "ping ssh df connman syslog xorg scp vnc date rpm dnf dmesg" Add your own test to the list of the by using the following: @@ -10024,7 +10031,7 @@ server_ip: The host's IP address, which is - usually used by the "smart" test + usually used by the "dnf" test suite. run(cmd, timeout=None): -- cgit v1.2.3-54-g00ecf