Skip to contentSkip to conversation

opkg: solve inconsistency of using different lists directories

PATCH New Alejandro Hernandez 1 participant 1 message Jul 31, 2015 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

PATCH 1/1 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]

---
 meta/recipes-devtools/opkg/opkg_0.2.4.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-devtools/opkg/opkg_0.2.4.bb +1 -1
index 56df920..b7574e5 100644
@@ -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
Signature · 1 line
1.8.4.5