nixpkgs

167,702 Commits 1 Branch 0 Tags

2 Commits

Author	SHA1	Message	Date
Sergei Maximov	05c8d5c88f	gem-config: add digest-sha3 `digest-sha3` is a C-extension gem which fails to build on Nix because it uses non-literals as format strings which is forbidden by the default Nix hardening settings. There is a pull request to fix that ([1]), but the gem seems to be abandoned. This PR disables the "format" hardening for `digest-sha3`. [1]: https://github.com/phusion/digest-sha3-ruby/pull/8	2019-01-18 13:48:48 +03:00
Sergei Maximov	a3bff35450	gem-config: support rbnacl v6.0.0 With the v6.0.0 release of the `rbnacl` gem, it does not longer depends on `rbnacl-libsodium` gem (which is now deprecated ([1])) to package the `libsodium` library and should use the one provided by the distribution; it raises an error if `rbnacl-libsodium` is detected ([2]). Unfortunately, default gem config patches `rbnacl` unconditionally ([3]), which means that newer versions of `rbnacl` fail at startup. [1]: https://github.com/crypto-rb/rbnacl-libsodium/issues/29 [2]: https://github.com/crypto-rb/rbnacl/blob/c176fc0bd8be74cf62c93a4b122e220ce4895348/lib/rbnacl.rb#L4-L8 [3]: https://github.com/NixOS/nixpkgs/blob/9fd099a6ae1690909ebf40145e4cdabd67179676/pkgs/development/ruby-modules/gem-config/default.nix#L300-L306	2019-01-18 11:04:54 +03:00

Author

SHA1

Message

Date

Sergei Maximov

05c8d5c88f

gem-config: add digest-sha3

`digest-sha3` is a C-extension gem which fails to build on Nix because
it uses non-literals as format strings which is forbidden by the default
Nix hardening settings. There is a pull request to fix that ([1]), but
the gem seems to be abandoned.

This PR disables the "format" hardening for `digest-sha3`.

[1]: https://github.com/phusion/digest-sha3-ruby/pull/8

2019-01-18 13:48:48 +03:00

Sergei Maximov

a3bff35450

gem-config: support rbnacl v6.0.0

With the v6.0.0 release of the `rbnacl` gem, it does not longer depends
on `rbnacl-libsodium` gem (which is now deprecated ([1])) to package the
`libsodium` library and should use the one provided by the distribution;
it raises an error if `rbnacl-libsodium` is detected ([2]).
Unfortunately, default gem config patches `rbnacl` unconditionally ([3]),
which means that newer versions of `rbnacl` fail at startup.

[1]: https://github.com/crypto-rb/rbnacl-libsodium/issues/29
[2]: https://github.com/crypto-rb/rbnacl/blob/c176fc0bd8be74cf62c93a4b122e220ce4895348/lib/rbnacl.rb#L4-L8
[3]: https://github.com/NixOS/nixpkgs/blob/9fd099a6ae1690909ebf40145e4cdabd67179676/pkgs/development/ruby-modules/gem-config/default.nix#L300-L306

2019-01-18 11:04:54 +03:00