summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools
diff options
context:
space:
mode:
authorAdrian Ratiu <adrian.ratiu@collabora.com>2019-07-17 00:55:58 +0300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-07-17 19:25:02 +0100
commit897483147f307aae627cf200d492aaff3b4bbef4 (patch)
tree715f2fb1a91fb58d8437495d1ff59f70d1ef6f61 /meta/recipes-devtools
parentab5a665612622f1106b37d1610ce5126aeabcb4c (diff)
downloadpoky-897483147f307aae627cf200d492aaff3b4bbef4.tar.gz
opkg/package/rootfs_ipk: allow overwriting OPKGLIBDIR
Some distributions for various reasons (like for example mounting a tmpfs over /var at runtime) can't use /var/lib to store the opkg metadata, so a different path is required to have a functioning package manager. ${localstatedir} can't be modified to something other than the hardcoded value in bitbake.conf because other recipes depending on it will fail to install. So the only recourse, which is also the least invasive, is to allow distros to overwrite the OPKGLIBDIR variable just like they are also allowed to overwrite OPKGBUILDCMD. (From OE-Core rev: 81eae383c287ad2e74321345c5eba862d5704cc4) Signed-off-by: Adrian Ratiu <adrian.ratiu@collabora.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools')
-rw-r--r--meta/recipes-devtools/opkg/opkg_0.4.1.bb2
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/recipes-devtools/opkg/opkg_0.4.1.bb b/meta/recipes-devtools/opkg/opkg_0.4.1.bb
index 663eaec346..6270862899 100644
--- a/meta/recipes-devtools/opkg/opkg_0.4.1.bb
+++ b/meta/recipes-devtools/opkg/opkg_0.4.1.bb
@@ -28,7 +28,7 @@ PACKAGES =+ "libopkg"
28inherit autotools pkgconfig systemd ptest 28inherit autotools pkgconfig systemd ptest
29 29
30target_localstatedir := "${localstatedir}" 30target_localstatedir := "${localstatedir}"
31OPKGLIBDIR = "${target_localstatedir}/lib" 31OPKGLIBDIR ??= "${target_localstatedir}/lib"
32 32
33PACKAGECONFIG ??= "libsolv" 33PACKAGECONFIG ??= "libsolv"
34 34