From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2 V5] systemd: Upgrade to 232
Date: Thu, 1 Dec 2016 09:28:58 +0000 [thread overview]
Message-ID: <6bd14a6cb6904f409632cae7f29ae287@XBOX02.axis.com> (raw)
In-Reply-To: <20161128212606.26139-1-raj.khem@gmail.com>
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Khem Raj
> Sent: den 28 november 2016 22:26
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH 2/2 V5] systemd: Upgrade to 232
>
> * Drop support for rcS.d SysV init scripts.
> These are prone to cause dependency loops, and almost all packages
> with
> rcS scripts now ship a native systemd service.
>
> * Drop mount propagation patch, it only happens with libseccomp, OE
> doesnt
> enable it
>
> * kdbus option has disappeared from configure
>
> * Ignore dev-so for PN now since systemd introduced private .so see
> https://github.com/systemd/systemd/issues/3810
Rather than adding:
INSANE_SKIP_${PN} += "dev-so"
would it not be more appropriate to add
${systemd_unitdir}/libsystemd-shared.so to FILES_${PN}-dev, i.e.:
-FILES_${PN}-dev += "${base_libdir}/security/*.la ${datadir}/dbus-1/interfaces/ ${sysconfdir}/rpm/macros.systemd"
+FILES_${PN}-dev += "${base_libdir}/security/*.la ${datadir}/dbus-1/interfaces/ ${sysconfdir}/rpm/macros.systemd ${systemd_unitdir}/libsystemd-shared.so"
The binaries are linked with libsystemd-shared-232.so which ends up in
${PN} as usual.
> * Add libnss* to PACKAGES_DYNAMIC for libnss-resolve to work correctly
>
> * Forward port systemd-boot patches to systemd-232
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
//Peter
next prev parent reply other threads:[~2016-12-01 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 21:26 [PATCH 2/2 V5] systemd: Upgrade to 232 Khem Raj
2016-12-01 9:28 ` Peter Kjellerstedt [this message]
2016-12-01 16:50 ` Khem Raj
2016-12-02 10:41 ` Peter Kjellerstedt
2016-12-01 20:22 ` Burton, Ross
2016-12-01 22:21 ` Khem Raj
2016-12-01 22:28 ` Khem Raj
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=6bd14a6cb6904f409632cae7f29ae287@XBOX02.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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