aboutsummaryrefslogtreecommitdiff
path: root/pkgs/development/libraries/libseccomp (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Merge staging-next into stagingFrederik Rietdijk2020-11-271-2/+2
|\
| * Merge master into staging-nextFrederik Rietdijk2020-11-271-2/+2
| |\
| | * utillinux: rename to util-linuxGraham Christensen2020-11-241-2/+2
| | |
* | | Merge pull request #104551 from r-ryantm/auto-update/libseccompMario Rodas2020-11-241-2/+2
|\ \ \ | |/ / |/| | libseccomp: 2.5.0 -> 2.5.1
| * | libseccomp: 2.5.0 -> 2.5.1R. RyanTM2020-11-221-2/+2
| |/
* / pythonPackages: add new 'seccomp' libraryAustin Seipp2020-11-201-1/+8
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As requested in #99553. Closes #99553. Libraries that install python modules as part of the build are problematic, because they either - only support a single python version, because the input for pythonPackages gets fixed in all-packages.nix, or - need to be rebuild the underlying C code for *every* python version resulting in libfoo-python37, libfoo-python38, and so on We would prefer to use the second approach because it works correctly for all versions of python. However, it creates duplicate copies of libseccomp.so and that can be expensive. Instead we 'deduplicate' the copies of libseccomp.so by - attaching a new $pythonsrc output to the libseccomp deriv, and - exposing a new 'seccomp' package in python-packages.nix using libseccomp as input, and - having a custom python.nix derivation that builds the cython extension using libseccomp to get the python source and the package version This means we build 1 copy of the seccomp python package, one for each version of python, but all of those packages refer to a single instance of the libseccomp C library, giving us the best of both worlds. NOTE: because this requires changing the postInstall of libseccomp, it requires a mass rebuild. Signed-off-by: Austin Seipp <aseipp@pobox.com>
* libseccomp: move gpref from buildInputs to nativeBuildInputsChristian Kampka2020-08-311-2/+3
|
* libseccomp: disable RISC-V 32bit architectureSascha Grunert2020-08-261-0/+1
| | | | Signed-off-by: Sascha Grunert <sgrunert@suse.com>
* libseccomp: enable RISC-V architectureSascha Grunert2020-08-241-2/+0
| | | | Signed-off-by: Sascha Grunert <sgrunert@suse.com>
* libseccomp: 2.4.3 -> 2.5.0Sascha Grunert2020-08-241-4/+4
| | | | Signed-off-by: Sascha Grunert <sgrunert@suse.com>
* libseccomp: format with nixpkgs-fmtSascha Grunert2020-08-241-5/+7
| | | | Signed-off-by: Sascha Grunert <sgrunert@suse.com>
* libseccomp: 2.4.2 -> 2.4.3R. RyanTM2020-03-071-2/+2
|
* libseccomp: 2.4.1 -> 2.4.2R. RyanTM2019-11-301-2/+2
|
* treewide: name -> pname (easy cases) (#66585)volth2019-08-151-1/+1
| | | | | | | | | treewide replacement of stdenv.mkDerivation rec { name = "*-${version}"; version = "*"; to pname
* libseccomp: mark bad platformsMatthew Bauer2019-05-021-1/+5
| | | | taken from https://github.com/seccomp/libseccomp#supported-architectures
* libseccomp: 2.4.0 -> 2.4.1Will Dietz2019-04-181-2/+2
| | | | https://github.com/seccomp/libseccomp/releases/tag/v2.4.1
* libseccomp: 2.3.3 -> 2.4.0Will Dietz2019-03-141-2/+2
| | | | https://github.com/seccomp/libseccomp/releases/tag/v2.4.0
* treewide: remove wkennington as maintainerJörg Thalheim2019-01-261-1/+1
| | | | | | He prefers to contribute to his own nixpkgs fork triton. Since he is still marked as maintainer in many packages this leaves the wrong impression he still maintains those.
* libseccomp: make tests run, but dependency cycleJan Malakhovski2018-08-111-1/+4
|
* libseccomp: Disable only on RISC-V if Linux.Shea Levy2018-03-271-0/+1
| | | | | | The isSeccomputable flag treated Linux without seccomp as just a normal variant, when it really should be treated as a special case incurring complexity debt to support.
* libseccomp: Use multiple outputsEelco Dolstra2018-02-221-0/+2
|
* libseccomp: 2.3.2 -> 2.3.3Franz Pletz2018-01-281-2/+2
|
* libseccomp: Fix RPATHEelco Dolstra2017-05-041-4/+2
| | | | | | | | Ensure that bin/scmp_sys_resolver doesn't have $TMPDIR in its RPATH. I can't reproduce the issue reported in 98edb2436861e18ef73076c5a894a6a90e7db71c that required the addition of a wrapper script. It seems to work fine without.
* libseccomp: 2.3.1 -> 2.3.2 + fixed scmp_sys_resolverRenaud2017-03-171-7/+11
| | | | | `libseccomp` is updated to 2.3.2 `scmp_sys_resolver` is fixed (it could not find libseccomp.so.2 shared library before)
* libseccomp: 2.3.0 -> 2.3.1Franz Pletz2016-08-251-2/+2
|
* Captialize meta.description of all packagesBjørn Forsman2016-06-201-1/+1
| | | | | | | | | | | | | | | | In line with the Nixpkgs manual. A mechanical change, done with this command: find pkgs -name "*.nix" | \ while read f; do \ sed -e 's/description\s*=\s*"\([a-z]\)/description = "\u\1/' -i "$f"; \ done I manually skipped some: * Descriptions starting with an abbreviation, a user name or package name * Frequently generated expressions (haskell-packages.nix)
* libseccomp: 2.2.3 -> 2.3.0Franz Pletz2016-05-031-2/+2
|
* libseccomp: Fix hashEelco Dolstra2015-09-081-1/+1
|
* Merge branch 'master' into systemd-219Eelco Dolstra2015-09-071-2/+2
|\ | | | | | | | | | | | | | | | | Conflicts: nixos/modules/system/boot/systemd.nix pkgs/applications/networking/p2p/transmission/default.nix pkgs/development/libraries/libseccomp/default.nix pkgs/os-specific/linux/systemd/default.nix pkgs/top-level/all-packages.nix
| * nixpkgs: libseccomp 2.2.1 -> 2.2.3Austin Seipp2015-07-201-2/+2
| | | | | | | | Signed-off-by: Austin Seipp <aseipp@pobox.com>
| * libseccomp: 2.2.0 -> 2.2.1William A. Kennington III2015-05-201-2/+2
| |
* | libseccomp: Update to 2.2.1Eelco Dolstra2015-05-221-9/+8
|/
* libseccomp: 2.1.1 -> 2.2.0William A. Kennington III2015-03-261-18/+14
|
* libseccomp: attempt to fix Hydra buildAustin Seipp2014-04-111-1/+2
| | | | Signed-off-by: Austin Seipp <aseipp@pobox.com>
* libseccomp: version 2.1.1Austin Seipp2014-04-081-0/+30
Signed-off-by: Austin Seipp <aseipp@pobox.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-01 03:37:33 +0000