libseccomp

Edit Package libseccomp
No description set
Refresh
Refresh
Source Files
Filename Size Changed
baselibs.conf 0000000012 12 Bytes
libseccomp-2.3.2.tar.gz 0000559238 546 KB
libseccomp-2.3.2.tar.gz.SHA256SUM.asc 0000000972 972 Bytes
libseccomp.changes 0000006379 6.23 KB
libseccomp.spec 0000004896 4.78 KB
no-static.diff 0000000754 754 Bytes
Revision 52 (latest revision is 105)
Marcus Meissner's avatar Marcus Meissner (msmeissn) accepted request 497120 from Tomáš Chvátal's avatar Tomáš Chvátal (scarabeus_iv) (revision 52)
- Update to release 2.3.2:
  * Achieved full compliance with the CII Best Practices program
  * Added Travis CI builds to the GitHub repository
  * Added code coverage reporting with the "--enable-code-coverage" configure
    flag and added Coveralls to the GitHub repository
  * Updated the syscall tables to match Linux v4.10-rc6+
  * Support for building with Python v3.x
  * Allow rules with the -1 syscall if the SCMP\_FLTATR\_API\_TSKIP attribute is
    set to true
  * Several small documentation fixes
- Remove service file as we are not based on git
Comments 2

Jochen Breuer's avatar

While the spec mentions the python bindings for seccomp, it's not actually enabled with --enable-python during ./configure. Also static builds are disable with --disable-static, which prevents setup.py from running because libseccomp.a is missing. Can we have both, static an dynamic binaries somehow?


Jan Engelhardt's avatar
  1. Removed the package def, because if anything, it should be replaced with the python macro magic for multipython builds.
  2. If setup.py requires libseccomp.a, then setup is broken and needs fixing. Reading .la files to determine the real lib name is not hard.
openSUSE Build Service is sponsored by