From: Graham Gower <graham.gower@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH] package_ipk.bbclass: add lists_dir to sysroots' /etc/opkg.conf
Date: Thu, 05 Aug 2010 16:01:50 +0930 [thread overview]
Message-ID: <4C5A5AD6.9090409@gmail.com> (raw)
This makes the sysroots' /etc/opkg.conf agree with opkg-collateral on where
the package lists database should be found. Fixes a problem whereby opkg
cannot find the package lists after opkg-collateral is installed.
This fixes the same problem as acc720fa80227d08fd15764117e0c34e2387e804.
But since that doesn't take into account other dependencies bringing
opkg-collateral into the image, it doesn't solve the problem in all
cases and could probably be reverted.
This is a bit messy, having hardcoded /var/lib/opkg as the lists_dir
in multiple locations. Other suggestions welcome.
I'm not sure its all that necessary to be using /usr/lib/opkg other
than for backwards compatibility with existing installations.
Signed-off-by: Graham Gower <graham.gower@gmail.com>
---
classes/package_ipk.bbclass | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/classes/package_ipk.bbclass b/classes/package_ipk.bbclass
index cd01496..3d70181 100644
--- a/classes/package_ipk.bbclass
+++ b/classes/package_ipk.bbclass
@@ -132,6 +132,9 @@ package_generate_ipkg_conf () {
echo "src oe-${SDK_SYS}-sdk-$arch file:${DEPLOY_DIR_IPK}/${SDK_SYS}-sdk-$arch" >> ${IPKGCONF_CANSDK}
fi
done
+ echo "lists_dir ext /var/lib/opkg" >> ${IPKGCONF_TARGET}
+ echo "lists_dir ext /var/lib/opkg" >> ${IPKGCONF_SDK}
+ echo "lists_dir ext /var/lib/opkg" >> ${IPKGCONF_CANSDK}
}
python do_package_ipk () {
--
1.7.1
next reply other threads:[~2010-08-05 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 6:31 Graham Gower [this message]
2010-08-05 7:20 ` [PATCH] package_ipk.bbclass: add lists_dir to sysroots' /etc/opkg.conf Martin Jansa
2010-08-05 14:14 ` Chris Larson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C5A5AD6.9090409@gmail.com \
--to=graham.gower@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.