Hello community,

here is the log from the commit of package lxqt-globalkeys-qt5 for 
openSUSE:Factory checked in at 2015-02-05 11:00:00
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/lxqt-globalkeys-qt5 (Old)
 and      /work/SRC/openSUSE:Factory/.lxqt-globalkeys-qt5.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "lxqt-globalkeys-qt5"

Changes:
--------
--- /work/SRC/openSUSE:Factory/lxqt-globalkeys-qt5/lxqt-globalkeys-qt5.changes  
2015-02-03 11:40:06.000000000 +0100
+++ 
/work/SRC/openSUSE:Factory/.lxqt-globalkeys-qt5.new/lxqt-globalkeys-qt5.changes 
    2015-02-05 11:00:01.000000000 +0100
@@ -1,0 +2,5 @@
+Tue Feb  3 11:16:45 UTC 2015 - [email protected]
+
+- aarch64 ppc64 ppc64le have /usr/lib64 too 
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ lxqt-globalkeys-qt5.spec ++++++
--- /var/tmp/diff_new_pack.ZcLZZd/_old  2015-02-05 11:00:02.000000000 +0100
+++ /var/tmp/diff_new_pack.ZcLZZd/_new  2015-02-05 11:00:02.000000000 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package lxqt-globalkeys-qt5
 #
-# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany.
+# Copyright (c) 2015 SUSE LINUX Products GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -69,10 +69,10 @@
 pushd build
 cmake \
       -DUSE_QT5=ON \
-      -DCMAKE_INSTALL_PREFIX:PATH=/usr \
-%ifarch x86_64
-      -DCMAKE_INSTALL_LIBDIR:PATH=/usr/lib64 \
-      -DLIB_INSTALL_DIR:PATH=/usr/lib64 \
+      -DCMAKE_INSTALL_PREFIX:PATH=%{_prefix} \
+      -DCMAKE_INSTALL_LIBDIR:PATH=%{_libdir} \
+      -DLIB_INSTALL_DIR:PATH=%{_libdir} \
+%ifarch x86_64 aarch64 ppc64 ppc64le
       -DLIB_SUFFIX=64 \
 %endif
       ..

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to