public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] systemd: Enable build of compat libs.
Date: Fri, 16 Oct 2015 18:16:05 +0200	[thread overview]
Message-ID: <1445012165.2021.11.camel@ipfire.org> (raw)
In-Reply-To: <1445009848.18375.72.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2446 bytes --]

Hello Michael,

currently the own known package in IPFire 3 is the strongswan package
(also the latest available version), which requires those compat libs
during configure and building.

Perhaps there are some more packages which may be include in the future
affected by this problem and requires those libs to build. 

An additional reason for adding the compat libraries would be keep the
compatiblity with some old packages which have been compiled and linked
against systemd < 215 which was the last version that provided these
libs. Otherwise they are not installable and useable anymore.

Best regards,

-Stefan
> What packages are depending on this? Couldn't these just be
> recompiled?
> 
> -Michael
> 
> On Fri, 2015-10-16 at 17:35 +0200, Stefan Schantl wrote:
> > Some software out there is still linking against the old
> > systemd libraries which now are shipped in an own package.
> > 
> > Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> > ---
> >  systemd/systemd.nm | 24 +++++++++++++++++++++++-
> >  1 file changed, 23 insertions(+), 1 deletion(-)
> > 
> > diff --git a/systemd/systemd.nm b/systemd/systemd.nm
> > index 7112a3c..7346c09 100644
> > --- a/systemd/systemd.nm
> > +++ b/systemd/systemd.nm
> > @@ -5,7 +5,7 @@
> >  
> >  name       = systemd
> >  version    = 221
> > -release    = 1
> > +release    = 2
> >  
> >  maintainer = Stefan Schantl <stefan.schantl(a)ipfire.org>
> >  groups     = System/Base
> > @@ -60,6 +60,7 @@ build
> >  		--with-sysvrcnd-path= \
> >  		--enable-introspection \
> >  		--enable-zlib \
> > +		--enable-compat-libs \
> >  		--disable-smack \
> >  		--disable-backlight \
> >  		--disable-firstboot \
> > @@ -358,9 +359,30 @@ packages
> >  		end
> >  	end
> >  
> > +	package %{name}-compat-libs
> > +		summary = systemd compatibility libraries.
> > +		description
> > +			Compatibility libraries for systemd. If
> > your
> > package requires this
> > +			package, you need to update your link
> > options and build.
> > +		end
> > +
> > +		requires
> > +			%{name}-libs = %{thisver}
> > +		end
> > +
> > +		files
> > +			%{libdir}/libsystemd-daemon.so.*
> > +			%{libdir}/libsystemd-login.so.*
> > +			%{libdir}/libsystemd-journal.so.*
> > +			%{libdir}/libsystemd-id128.so.*
> > +		end
> > +	end
> > +
> >  	package %{name}-devel
> >  		template DEVEL
> >  
> > +		requires += %{name}-compat-libs = %{thisver}
> > +
> >  		files += %{prefix}/lib/pakfire/macros/
> >  	end

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-10-16 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 15:35 Stefan Schantl
2015-10-16 15:37 ` Michael Tremer
2015-10-16 16:16   ` Stefan Schantl [this message]
2015-10-16 16:17     ` Michael Tremer

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=1445012165.2021.11.camel@ipfire.org \
    --to=stefan.schantl@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