nordic-dev.net/nixpkgs
nordic-dev.net/nixpkgs
2
0
Fork 0
mirror of https://github.com/NixOS/nixpkgs.git synced 2024-12-26 15:44:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
9bc67194e0
nixpkgs/pkgs/tools/networking/s6-networking/default.nix

67 lines
1.9 KiB
Nix
Raw Normal View History

treewide: remove redundant stdenv
2021-03-26 05:13:53 +00:00
{ lib, skawarePackages
s6-networking: add ssl support (libressl by default) For now there’s only support for libressl, but it is built in a way that makes adding support for e.g. bearssl trivial.
2018-07-27 07:10:10 +00:00
# Whether to build the TLS/SSL tools and what library to use
s6-networking: default to bearssl 18·27 <Profpatsch> skarnet: would you recommend putting bearssl as the default backend for s6-networking? 18·27 <Profpatsch> uh, bearssl isn’t even packaged 18·27 <Profpatsch> yak shave 18·28 <Profpatsch> skarnet: The current backend uses libressl 18·29 <@skarnet> well at least CAFILE works 18·29 <@skarnet> but yes, I would recommend putting bearssl as the default backend
2021-03-21 18:56:02 +00:00
# acceptable values: "bearssl", "libressl", false
, sslSupport ? "bearssl" , libressl, bearssl
s6-networking: add ssl support (libressl by default) For now there’s only support for libressl, but it is built in a way that makes adding support for e.g. bearssl trivial.
2018-07-27 07:10:10 +00:00
}:
s6-networking: new package s6-networking is a suite of small networking utilities for Unix systems including UCSPI Unix and TCP tools, access control tools, and network time management utilities.
2014-08-30 05:07:45 +00:00
skawarePackages: factor out the common parts Introduce a `skawarePackages.buildPackage` function that contains the common setup, removing a lot of duplication. In particular, we require that the build directory has to be empty after the `fixupPhase`, to make sure every relevant file is moved to the outputs. A next step would be to deduplicate the `configureFlags` attributes and only require a `skawareInputs` field.
2018-09-02 21:31:26 +00:00
with skawarePackages;
s6-networking: new package s6-networking is a suite of small networking utilities for Unix systems including UCSPI Unix and TCP tools, access control tools, and network time management utilities.
2014-08-30 05:07:45 +00:00
let
s6-networking: add ssl support (libressl by default) For now there’s only support for libressl, but it is built in a way that makes adding support for e.g. bearssl trivial.
2018-07-27 07:10:10 +00:00
sslSupportEnabled = sslSupport != false;
sslLibs = {
treewide: remove redundant quotes
2019-08-13 21:52:01 +00:00
libressl = libressl;
s6-networking: default to bearssl 18·27 <Profpatsch> skarnet: would you recommend putting bearssl as the default backend for s6-networking? 18·27 <Profpatsch> uh, bearssl isn’t even packaged 18·27 <Profpatsch> yak shave 18·28 <Profpatsch> skarnet: The current backend uses libressl 18·29 <@skarnet> well at least CAFILE works 18·29 <@skarnet> but yes, I would recommend putting bearssl as the default backend
2021-03-21 18:56:02 +00:00
bearssl = bearssl;
s6-networking: add ssl support (libressl by default) For now there’s only support for libressl, but it is built in a way that makes adding support for e.g. bearssl trivial.
2018-07-27 07:10:10 +00:00
};
in
assert sslSupportEnabled -> sslLibs ? ${sslSupport};
s6-networking: new package s6-networking is a suite of small networking utilities for Unix systems including UCSPI Unix and TCP tools, access control tools, and network time management utilities.
2014-08-30 05:07:45 +00:00
skawarePackages: factor out the common parts Introduce a `skawarePackages.buildPackage` function that contains the common setup, removing a lot of duplication. In particular, we require that the build directory has to be empty after the `fixupPhase`, to make sure every relevant file is moved to the outputs. A next step would be to deduplicate the `configureFlags` attributes and only require a `skawareInputs` field.
2018-09-02 21:31:26 +00:00
buildPackage {
pname = "s6-networking";
s6-networking: 2.4.1.0 -> 2.4.1.1 • skalibs dependency bumped to 2.10.0.3 • execline dependency bumped to 2.8.0.1 • s6 dependency bumped to 2.10.0.3 • s6-dns dependency bumped to 2.3.5.1 • LibreSSL optional dependency bumped to 3.2.5 • OpenSSL optional dependency bumped to 1.1.1k
2021-06-15 13:48:35 +00:00
version = "2.4.1.1";
sha256 = "0m55ibx7k2wgrqbpci1n667ij0h925ajzggxalq2pj65kmwcmyx3";
s6-networking: new package s6-networking is a suite of small networking utilities for Unix systems including UCSPI Unix and TCP tools, access control tools, and network time management utilities.
2014-08-30 05:07:45 +00:00
skawarePackages: factor out the common parts Introduce a `skawarePackages.buildPackage` function that contains the common setup, removing a lot of duplication. In particular, we require that the build directory has to be empty after the `fixupPhase`, to make sure every relevant file is moved to the outputs. A next step would be to deduplicate the `configureFlags` attributes and only require a `skawareInputs` field.
2018-09-02 21:31:26 +00:00
description = "A suite of small networking utilities for Unix systems";
s6-networking: new package s6-networking is a suite of small networking utilities for Unix systems including UCSPI Unix and TCP tools, access control tools, and network time management utilities.
2014-08-30 05:07:45 +00:00
skarnet software: rename attributes and split outputs Change the attribute names of camelCased utils to kebab-case to improve consistency. Split every package into multiple outputs where possible.
2018-07-22 15:03:19 +00:00
outputs = [ "bin" "lib" "dev" "doc" "out" ];
skaware: update tools & libraries to summer 2018 release https://www.mail-archive.com/skaware@list.skarnet.org/msg01217.html No support for yet.
2018-09-02 15:04:57 +00:00
# TODO: nsss support
Update skarnet.org software for 2.0 release. New build system using configure script and GNU Make 4.0, and new releases of the following using the new build system: execline 2.0.0.0 s6 2.0.0.0 s6-dns 2.0.0.0 s6-linux-utils 2.0.0.0 s6-networking 2.0.0.0 s6-portable-utils 2.0.0.0 skalibs 2.0.0.0
2014-12-23 16:06:27 +00:00
configureFlags = [
skarnet software: rename attributes and split outputs Change the attribute names of camelCased utils to kebab-case to improve consistency. Split every package into multiple outputs where possible.
2018-07-22 15:03:19 +00:00
"--libdir=\${lib}/lib"
"--libexecdir=\${lib}/libexec"
"--dynlibdir=\${lib}/lib"
"--bindir=\${bin}/bin"
"--includedir=\${dev}/include"
"--with-sysdeps=${skalibs.lib}/lib/skalibs/sysdeps"
"--with-include=${skalibs.dev}/include"
"--with-include=${execline.dev}/include"
"--with-include=${s6.dev}/include"
"--with-include=${s6-dns.dev}/include"
"--with-lib=${skalibs.lib}/lib"
"--with-lib=${execline.lib}/lib"
"--with-lib=${s6.out}/lib"
"--with-lib=${s6-dns.lib}/lib"
"--with-dynlib=${skalibs.lib}/lib"
"--with-dynlib=${execline.lib}/lib"
"--with-dynlib=${s6.out}/lib"
"--with-dynlib=${s6-dns.lib}/lib"
set target for darwin binary compat in skarnet.org packages skalibs: execline: s6-dns: s6-networking: s6-portable-utils: s6-rc: s6: The above software uses the target triplet from `cc -dumpmachine` as a binary compatibility check. However, on darwin, the output includes the darwin version number, which leads to build failures against a binary skalibs package built a different version of darwin than the current system. Explicitly setting target ensures code can be compiled against a skalibs binary built on a different version of darwin. See http://www.skarnet.org/cgi-bin/archive.cgi?1:mss:623:heiodchokfjdkonfhdph
2016-04-01 15:20:13 +00:00
]
s6-networking: add ssl support (libressl by default) For now there’s only support for libressl, but it is built in a way that makes adding support for e.g. bearssl trivial.
2018-07-27 07:10:10 +00:00
++ (lib.optionals sslSupportEnabled [
"--enable-ssl=${sslSupport}"
"--with-include=${lib.getDev sslLibs.${sslSupport}}/include"
"--with-lib=${lib.getLib sslLibs.${sslSupport}}/lib"
skawarePackages: factor out the common parts Introduce a `skawarePackages.buildPackage` function that contains the common setup, removing a lot of duplication. In particular, we require that the build directory has to be empty after the `fixupPhase`, to make sure every relevant file is moved to the outputs. A next step would be to deduplicate the `configureFlags` attributes and only require a `skawareInputs` field.
2018-09-02 21:31:26 +00:00
"--with-dynlib=${lib.getLib sslLibs.${sslSupport}}/lib"
]);
s6-networking: new package s6-networking is a suite of small networking utilities for Unix systems including UCSPI Unix and TCP tools, access control tools, and network time management utilities.
2014-08-30 05:07:45 +00:00
skarnet software: rename attributes and split outputs Change the attribute names of camelCased utils to kebab-case to improve consistency. Split every package into multiple outputs where possible.
2018-07-22 15:03:19 +00:00
postInstall = ''
skawarePackages: factor out the common parts Introduce a `skawarePackages.buildPackage` function that contains the common setup, removing a lot of duplication. In particular, we require that the build directory has to be empty after the `fixupPhase`, to make sure every relevant file is moved to the outputs. A next step would be to deduplicate the `configureFlags` attributes and only require a `skawareInputs` field.
2018-09-02 21:31:26 +00:00
# remove all s6 executables from build directory
rm $(find -name "s6-*" -type f -mindepth 1 -maxdepth 1 -executable)
rm minidentd
s6-networking: default to bearssl 18·27 <Profpatsch> skarnet: would you recommend putting bearssl as the default backend for s6-networking? 18·27 <Profpatsch> uh, bearssl isn’t even packaged 18·27 <Profpatsch> yak shave 18·28 <Profpatsch> skarnet: The current backend uses libressl 18·29 <@skarnet> well at least CAFILE works 18·29 <@skarnet> but yes, I would recommend putting bearssl as the default backend
2021-03-21 18:56:02 +00:00
rm libs6net.* libstls.* libs6tls.* libsbearssl.*
skawarePackages: factor out the common parts Introduce a `skawarePackages.buildPackage` function that contains the common setup, removing a lot of duplication. In particular, we require that the build directory has to be empty after the `fixupPhase`, to make sure every relevant file is moved to the outputs. A next step would be to deduplicate the `configureFlags` attributes and only require a `skawareInputs` field.
2018-09-02 21:31:26 +00:00
skarnet software: rename attributes and split outputs Change the attribute names of camelCased utils to kebab-case to improve consistency. Split every package into multiple outputs where possible.
2018-07-22 15:03:19 +00:00
mv doc $doc/share/doc/s6-networking/html
'';
s6-networking: new package s6-networking is a suite of small networking utilities for Unix systems including UCSPI Unix and TCP tools, access control tools, and network time management utilities.
2014-08-30 05:07:45 +00:00
}
Reference in New Issue Copy Permalink