From: Saul Wold <sgw@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] util-linux: Use PACKAGECONFIG to control pam and system config options
Date: Thu, 25 Jul 2013 07:17:59 -0700 [thread overview]
Message-ID: <51F13397.8030500@linux.intel.com> (raw)
In-Reply-To: <4F2BF532-D3A4-431E-8905-E4F33FBF80D5@dominion.thruhere.net>
On 07/25/2013 06:02 AM, Koen Kooi wrote:
>
>
>
> Op 25 jul. 2013, om 14:58 heeft Koen Kooi <koen@dominion.thruhere.net> het volgende geschreven:
>
>>
>> Op 10 jul. 2013, om 18:26 heeft Enrico Scholz <enrico.scholz@sigma-chemnitz.de> het volgende geschreven:
>>
>>> Saul Wold <sgw-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> writes:
>>>
>>>> The PACKAGECONFIG will ensure consistent enabling and disabling of the pam and systemd related
>>>> options for configure and the correct dependencies
>>>>
>>>> v2: fixed PACKAGECONFIG line continuation grammar
>>>> added _class-target for PACKAGECONFIG to work on target only
>>>> ...
>>>> +PACKAGECONFIG_class-target ??= "${@base_contains('DISTRO_FEATURES', 'pam', 'pam', '', d)} \
>>>> + ${@base_contains('DISTRO_FEATURES', 'systemd', 'systemd', '', d)} "
>>>
>>> This does not work here. d.getVar('PACKAGECONFIG', True) evaluates to 'None'
>>> in the anonymous python function in base.bbclass so that non-systemd options
>>> are selected in systemd distributions and packaging fails in a sanity check.
>>>
>>> Using the less weak '?=' operator makes thing work as expected.
>>
>> And a different version of this patch got merged:
>>
>> https://github.com/openembedded/oe-core/commit/7cde7c639c53724327d981cbc0db5e123607de1c
>>
>> Which has the following bug:
>>
>> PACKAGECONFIG_class-target ??= "${@base_contains('DISTRO_FEATURES', 'pam', 'libpam', '', d)} \
>> [..]
>> PACKAGECONFIG[pam] = "--enable-su --enable-runuser,--disable-su --disable-runuser, pam,"
>>
>> It sets 'libpam' as PACKAGECONFIG option, but the option is actually named 'pam'. The patches posted to this list don't seem to have this bug.
>
> Here's what I used with dylan + backports:
>
> commit 2f318d0f9627e1872732db1ecafaed9caeb68ebf
> Author: Koen Kooi <koen@dominion.thruhere.net>
> Date: Thu Jul 25 14:58:27 2013 +0200
>
> util-linux: fix PACKAGECONFIG options
>
> The ??= operator is too weak and it's setting a non-existent PACKAGECONFIG option ('libpam' instead of 'pam').
>
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
>
Koen,
Good catch, can you send this as a proper patch to the OE-Core list also.
Thanks
Sau!
> diff --git a/meta/recipes-core/util-linux/util-linux.inc b/meta/recipes-core/util-linux/util-linux.inc
> index d373cec..3d1198a 100644
> --- a/meta/recipes-core/util-linux/util-linux.inc
> +++ b/meta/recipes-core/util-linux/util-linux.inc
> @@ -47,9 +47,9 @@ EXTRA_OECONF = "--libdir=${base_libdir} --disable-use-tty-group \
> --enable-libuuid --enable-libblkid --enable-fsck --without-udev \
> usrsbin_execdir='${sbindir}' \
> "
> -PACKAGECONFIG_class-target ??= "${@base_contains('DISTRO_FEATURES', 'pam', 'libpam', '', d)} \
> +PACKAGECONFIG_class-target ?= "${@base_contains('DISTRO_FEATURES', 'pam', 'pam', '', d)} \
> ${@base_contains('DISTRO_FEATURES', 'systemd', 'systemd', '', d)} "
> -PACKAGECONFIG[pam] = "--enable-su --enable-runuser,--disable-su --disable-runuser, pam,"
> +PACKAGECONFIG[pam] = "--enable-su --enable-runuser,--disable-su --disable-runuser, libpam,"
>
> # Respect the systemd feature for uuidd
> PACKAGECONFIG[systemd] = "--enable-socket-activation --with-systemdsystemunitdir=${systemd_unitdir}/system/, --disable-socket-activation --without-systemdsystemunitdir"
>
>
>
>
next prev parent reply other threads:[~2013-07-25 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 23:10 [PATCH v2] util-linux: Use PACKAGECONFIG to control pam and system config options Saul Wold
2013-07-10 16:26 ` Enrico Scholz
2013-07-25 12:58 ` Koen Kooi
2013-07-25 13:02 ` Koen Kooi
2013-07-25 14:17 ` Saul Wold [this message]
2013-07-25 15:58 ` Enrico Scholz
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=51F13397.8030500@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=enrico.scholz@sigma-chemnitz.de \
--cc=koen@dominion.thruhere.net \
--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