Please login to access the resource

libseccomp

Edit Package libseccomp
No description set
Refresh
Refresh
Source Files
Filename Size Changed
baselibs.conf 0000000012 12 Bytes
libseccomp-2.5.0.tar.gz 0000638793 624 KB
libseccomp-2.5.0.tar.gz.asc 0000000833 833 Bytes
libseccomp.changes 0000011305 11 KB
libseccomp.keyring 0000003139 3.07 KB
libseccomp.spec 0000004093 4 KB
Revision 77 (latest revision is 105)
Marcus Meissner's avatar Marcus Meissner (msmeissn) accepted request 833010 from Ralf Haferkamp's avatar Ralf Haferkamp (rhafer) (revision 77)
- Update to release 2.5.0
  * Add support for the seccomp user notifications, see the
    seccomp_notify_alloc(3), seccomp_notify_receive(3),
    seccomp_notify_respond(3) manpages for more information
  * Add support for new filter optimization approaches, including a balanced
    tree optimization, see the SCMP_FLTATR_CTL_OPTIMIZE filter attribute for
    more information
  * Add support for the 64-bit RISC-V architecture
  * Performance improvements when adding new rules to a filter thanks to the
    use of internal shadow transactions and improved syscall lookup tables
  * Properly document the libseccomp API return values and include them in the
    stable API promise
  * Improvements to the s390 and s390x multiplexed syscall handling
  * Multiple fixes and improvements to the libseccomp manpages
  * Moved from manually maintained syscall tables to an automatically generated
    syscall table in CSV format
  * Update the syscall tables to Linux v5.8.0-rc5
  * Python bindings and build now default to Python 3.x
  * Improvements to the tests have boosted code coverage to over 93%
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