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) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
5c76072804
commit
e87b533b2f
|
@ -45,7 +45,7 @@ EXTRA_OECONF = "\
|
|||
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
|
||||
|
|
Loading…
Reference in New Issue