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.
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
/tmp/tmp.c5vXLPpHST /home/ryantm/.cache/nixpkgs
/home/ryantm/.cache/nixpkgs
- ran `/nix/store/w6nqi0pjm3bm0v1kcxk9v1ndj0qnjg6z-librsync-2.0.2/bin/rdiff -h` got 0 exit code
- ran `/nix/store/w6nqi0pjm3bm0v1kcxk9v1ndj0qnjg6z-librsync-2.0.2/bin/rdiff --help` got 0 exit code
- ran `/nix/store/w6nqi0pjm3bm0v1kcxk9v1ndj0qnjg6z-librsync-2.0.2/bin/rdiff -V` and found version 2.0.2
- ran `/nix/store/w6nqi0pjm3bm0v1kcxk9v1ndj0qnjg6z-librsync-2.0.2/bin/rdiff --version` and found version 2.0.2
- found 2.0.2 with grep in /nix/store/w6nqi0pjm3bm0v1kcxk9v1ndj0qnjg6z-librsync-2.0.2
- found 2.0.2 in filename of file in /nix/store/w6nqi0pjm3bm0v1kcxk9v1ndj0qnjg6z-librsync-2.0.2
- directory tree listing: https://gist.github.com/aef3b835949789ba889040112d401160
The following parameters are now available:
* hardeningDisable
To disable specific hardening flags
* hardeningEnable
To enable specific hardening flags
Only the cc-wrapper supports this right now, but these may be reused by
other wrappers, builders or setup hooks.
cc-wrapper supports the following flags:
* fortify
* stackprotector
* pie (disabled by default)
* pic
* strictoverflow
* format
* relro
* bindnow
Without this, if compiled with clang, all static functions do not end
up in the resultant shared library due to clang defaulting to c99.
The simple fix is to adjust CFLAGS, otherwise one needs to patch
a lot of inline's away needlessly.
