From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] systemd: Allow RPATH.
Date: Fri, 16 Dec 2016 10:39:15 +0000 [thread overview]
Message-ID: <1481884755.13949.284.camel@ipfire.org> (raw)
In-Reply-To: <1481820949-27395-1-git-send-email-stefan.schantl@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]
Hi,
I had to remove some whitespace issues. Please pay more attention to those next
time...
On Thu, 2016-12-15 at 17:55 +0100, Stefan Schantl wrote:
> The systemd tool now requires an rpath for libsystemd-shared
> library to run properly.
>
> Fixes #11272.
>
> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ---
> systemd/systemd.nm | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/systemd/systemd.nm b/systemd/systemd.nm
> index 074440e..e761bd5 100644
> --- a/systemd/systemd.nm
> +++ b/systemd/systemd.nm
> @@ -5,7 +5,7 @@
>
> name = systemd
> version = 232
> -release = 1
> +release = 2
>
> maintainer = Stefan Schantl <stefan.schantl(a)ipfire.org>
> groups = System/Base
> @@ -23,6 +23,11 @@ source_dl = https://github.com/%{name}/%{name}/archive/v%{
> version}.tar.gz#/
> build
> unitdir = %{prefix}/lib/systemd/system
>
> + # The tools which are shipped by systemd requires an rpath to
> + # the libsystemd-shared binary to run properly. So the macro for
> + # removing any rpath's have to be disabled.
> + MACRO_FIX_LIBTOOL = #Do nothing.
> +
Here.
> requires
> # Testsuite
> /usr/bin/getfacl
> @@ -199,6 +204,13 @@ create_groups
> getent group systemd-journal >/dev/null || /usr/sbin/groupadd -r
> systemd-journal
> end
>
> +quality-agent
> + whitelist_rpath
> + %{prefix}/lib/systemd
> + end
> +end
> +
> +
And here...
> packages
> package %{name}
> groups += Base
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-12-16 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 16:55 Stefan Schantl
2016-12-16 10:39 ` Michael Tremer [this message]
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=1481884755.13949.284.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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