Hello community,

here is the log from the commit of package libseccomp for openSUSE:Factory 
checked in at 2012-12-19 14:49:48
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libseccomp (Old)
 and      /work/SRC/openSUSE:Factory/.libseccomp.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "libseccomp", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/libseccomp/libseccomp.changes    2012-11-14 
16:50:54.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.libseccomp.new/libseccomp.changes       
2012-12-19 14:49:50.000000000 +0100
@@ -1,0 +2,11 @@
+Fri Dec 14 17:13:12 UTC 2012 - [email protected]
+
+- code is only x86 capable. Set ExclusiveArch: %{ix86} x86_64
+
+-------------------------------------------------------------------
+Thu Nov 15 00:49:40 UTC 2012 - [email protected]
+
+- Restore autotools patch (0001-build-use-autotools-as-build-system.patch)
+  that was previously embodied in the files in the tarball
+
+-------------------------------------------------------------------

New:
----
  0001-build-use-autotools-as-build-system.patch

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

Other differences:
------------------
++++++ libseccomp.spec ++++++
--- /var/tmp/diff_new_pack.0ih5YM/_old  2012-12-19 14:49:51.000000000 +0100
+++ /var/tmp/diff_new_pack.0ih5YM/_new  2012-12-19 14:49:51.000000000 +0100
@@ -24,12 +24,17 @@
 License:        LGPL-2.1
 Group:          Development/Libraries/C and C++
 Url:            http://sf.net/projects/seccomp/
-#DL-URL:       http://downloads.sf.net/libseccomp/libseccomp-%{version}.tar.gz
+
+#DL-URL:       http://downloads.sf.net/libseccomp/libseccomp-1.0.1.tar.gz
 #Git-Clone:    git://git.code.sf.net/p/libseccomp/libseccomp
 Source:         http://downloads.sf.net/libseccomp/libseccomp-%{version}.tar.gz
 Patch1:         0001-build-use-ac-variables-in-pkgconfig-file.patch
+Patch2:         0001-build-use-autotools-as-build-system.patch
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 BuildRequires:  pkgconfig
+BuildRequires:  python-Cython
+BuildRequires:  python-devel
+ExclusiveArch:  %ix86 x86_64
 
 %description
 The libseccomp library provides and easy to use, platform
@@ -51,6 +56,18 @@
 conventional function-call based filtering interface that should be
 familiar to, and easily adopted by application developers.
 
+%package -n python-%name
+Summary:        Python bindings for Seccomp (mode 2)
+Group:          Development/Languages/Python
+
+%description -n python-%name
+The libseccomp library provides and easy to use, platform
+independent, interface to the Linux Kernel's syscall filtering
+mechanism: seccomp. The libseccomp API is designed to abstract away
+the underlying BPF based syscall filter language and present a more
+conventional function-call based filtering interface that should be
+familiar to, and easily adopted by application developers.
+
 %package devel
 Summary:        Development files for libseccomp, an enhanced Seccomp (mode 2) 
helper library
 Group:          Development/Libraries/C and C++
@@ -68,17 +85,21 @@
 
 %prep
 %setup -q
-%patch -P 1 -p1
+%patch -P 1 -P 2 -p1
 
 %build
-%configure --includedir=%_includedir/%name-%version
-make V=1 %{?_smp_mflags}
+./autogen.sh;
+%configure --includedir=%_includedir/%name-%version --enable-python
+make V=1 %{?_smp_mflags};
 
 %install
 b="%buildroot";
 make install DESTDIR="$b";
 find "$b/%_libdir" -type f -name "*.la" -delete;
 
+%check
+make check
+
 %post -n %lname -p /sbin/ldconfig
 
 %postun -n %lname -p /sbin/ldconfig
@@ -87,10 +108,13 @@
 %defattr(-,root,root)
 %_libdir/%name.so.*
 
+%files -n python-libseccomp
+%defattr(-,root,root)
+
 %files devel
 %defattr(-,root,root)
 %_mandir/man3/seccomp_*.3*
-/usr/include/seccomp.h
+%_includedir/%name-%version
 %_libdir/%name.so
 %_libdir/pkgconfig/%name.pc
 

++++++ 0001-build-use-autotools-as-build-system.patch ++++++
++++ 1410 lines (skipped)

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

Reply via email to