summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlejandro Hernandez <alejandro.hernandez@linux.intel.com>2015-07-31 18:59:37 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-08-09 16:37:44 -0700
commit13e7544ae9191d2c3eca5e6ae52eb7c22f9bfebf (patch)
treeb4b5e73b74c74a5899cb6fe5adbd969644f2845d
parente2ca16c6d382a199314bb8affe85c23ac1862e8d (diff)
downloadast2050-yocto-poky-13e7544ae9191d2c3eca5e6ae52eb7c22f9bfebf.zip
ast2050-yocto-poky-13e7544ae9191d2c3eca5e6ae52eb7c22f9bfebf.tar.gz
opkg: solve inconsistency of using different lists directories
Default behavior of opkg was to use ${OPKGLIBDIR}/opkg/lists; but in our recipe we modify it to ${OPKGLIBDIR}/opkg/${OPKGLIBDIR}/opkg/, when appending package-management to IMAGE_FEATURES these lists are populated during build time (using the default directory), but since our config was different these populated lists were never used at runtime, this patch solves this inconsistency by using default behavior for both build time and runtime. [YOCTO #6966] (From OE-Core rev: a71b29ffc514892ca394fc8de275294b910586f0) (From OE-Core rev: f49fc4fc5c5f150dad9807d92239ada885bca5fd) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--meta/recipes-devtools/opkg/opkg_0.2.4.bb2
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/recipes-devtools/opkg/opkg_0.2.4.bb b/meta/recipes-devtools/opkg/opkg_0.2.4.bb
index 23a32e6..254ecfc 100644
--- a/meta/recipes-devtools/opkg/opkg_0.2.4.bb
+++ b/meta/recipes-devtools/opkg/opkg_0.2.4.bb
@@ -49,7 +49,7 @@ do_configure_prepend() {
do_install_append () {
install -d ${D}${sysconfdir}/opkg
install -m 0644 ${WORKDIR}/opkg.conf ${D}${sysconfdir}/opkg/opkg.conf
- echo "option lists_dir ${OPKGLIBDIR}/opkg" >>${D}${sysconfdir}/opkg/opkg.conf
+ echo "option lists_dir ${OPKGLIBDIR}/opkg/lists" >>${D}${sysconfdir}/opkg/opkg.conf
# We need to create the lock directory
install -d ${D}${OPKGLIBDIR}/opkg
OpenPOWER on IntegriCloud