Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Ratiu <adrian.ratiu@collabora.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] opkg/package/rootfs_ipk: allow overwriting OPKGLIBDIR
Date: Wed, 17 Jul 2019 14:52:21 +0300	[thread overview]
Message-ID: <87d0i8g9oq.fsf@collabora.com> (raw)
In-Reply-To: <CA+chaQdO2xLQR6z+xNTXYaqj4fvppguu6iVBZsLUXZLBgqC8xg@mail.gmail.com>

Hi

On Wed, 17 Jul 2019, Martin Jansa <martin.jansa@gmail.com> wrote:
> Why don't you overwrite it with an override? We're doing that 
> for years without any issues.

You mean a distro-wide override in a .conf?

Can you please point to an example?

>
> On Wed, Jul 17, 2019 at 12:01 AM Adrian Ratiu <adrian.ratiu@collabora.com>
> wrote:
>
>> 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.
>>
>> Signed-off-by: Adrian Ratiu <adrian.ratiu@collabora.com>
>> ---
>>  meta/classes/package_ipk.bbclass         | 2 +-
>>  meta/classes/rootfs_ipk.bbclass          | 2 +-
>>  meta/recipes-devtools/opkg/opkg_0.4.1.bb | 2 +-
>>  3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/meta/classes/package_ipk.bbclass
>> b/meta/classes/package_ipk.bbclass
>> index d1b317b42b..9f9da2f91d 100644
>> --- a/meta/classes/package_ipk.bbclass
>> +++ b/meta/classes/package_ipk.bbclass
>> @@ -14,7 +14,7 @@ OPKG_ARGS += "--force_postinstall
>> --prefer-arch-to-version"
>>  OPKG_ARGS += "${@['',
>> '--no-install-recommends'][d.getVar("NO_RECOMMENDATIONS") == "1"]}"
>>  OPKG_ARGS += "${@['', '--add-exclude ' + ' --add-exclude
>> '.join((d.getVar('PACKAGE_EXCLUDE') or
>> "").split())][(d.getVar("PACKAGE_EXCLUDE") or "").strip() != ""]}"
>>
>> -OPKGLIBDIR = "${localstatedir}/lib"
>> +OPKGLIBDIR ??= "${localstatedir}/lib"
>>
>>  python do_package_ipk () {
>>      workdir = d.getVar('WORKDIR')
>> diff --git a/meta/classes/rootfs_ipk.bbclass
>> b/meta/classes/rootfs_ipk.bbclass
>> index aabc370cfc..e73d2bfdae 100644
>> --- a/meta/classes/rootfs_ipk.bbclass
>> +++ b/meta/classes/rootfs_ipk.bbclass
>> @@ -21,7 +21,7 @@ OPKG_PREPROCESS_COMMANDS = ""
>>
>>  OPKG_POSTPROCESS_COMMANDS = ""
>>
>> -OPKGLIBDIR = "${localstatedir}/lib"
>> +OPKGLIBDIR ??= "${localstatedir}/lib"
>>
>>  MULTILIBRE_ALLOW_REP = "${OPKGLIBDIR}/opkg|/usr/lib/opkg"
>>
>> diff --git a/meta/recipes-devtools/opkg/opkg_0.4.1.bb
>> b/meta/recipes-devtools/opkg/opkg_0.4.1.bb
>> index 8c48d3097c..c663eff13b 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"
>>  inherit autotools pkgconfig systemd ptest
>>
>>  target_localstatedir := "${localstatedir}"
>> -OPKGLIBDIR = "${target_localstatedir}/lib"
>> +OPKGLIBDIR ??= "${target_localstatedir}/lib"
>>
>>  PACKAGECONFIG ??= "libsolv"
>>
>> --
>> 2.22.0
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>


  reply	other threads:[~2019-07-17 11:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16 21:55 [PATCH] opkg/package/rootfs_ipk: allow overwriting OPKGLIBDIR Adrian Ratiu
2019-07-17 11:12 ` Martin Jansa
2019-07-17 11:52   ` Adrian Ratiu [this message]
2019-07-17 12:17     ` Martin Jansa
2019-07-17 14:17       ` Adrian Ratiu
2019-07-17 14:41         ` Martin Jansa
2019-07-17 14:43           ` Martin Jansa

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=87d0i8g9oq.fsf@collabora.com \
    --to=adrian.ratiu@collabora.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox