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@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@ipfire.org groups = System/Base @@ -60,6 +60,7 @@ build --with-sysvrcnd-path= \ --enable-introspection \ --enable-zlib \
--enable-compat-libs \@@ -358,9 +359,30 @@ packages end end
- package %{name}-compat-libs
summary = systemd compatibility libraries.descriptionCompatibility libraries for systemd. Ifyour package requires this
package, you need to update your linkoptions and build.
endrequires%{name}-libs = %{thisver}endfiles%{libdir}/libsystemd-daemon.so.*%{libdir}/libsystemd-login.so.*%{libdir}/libsystemd-journal.so.*%{libdir}/libsystemd-id128.so.*endend
package %{name}-devel template DEVEL
requires += %{name}-compat-libs = %{thisver}files += %{prefix}/lib/pakfire/macros/ end