skawarePackages: add manpages to their respective packages
For a while now, we’ve had these separate derivations for the skaware
manpages.
That was fine in the beginning, because it was not entirely clear
whether the manpage project would be long-lived. Given that the
collection of third-party manpages is now extensive and updated
regularly, plus it is sanctioned by skarnet, we can remove this
additional hurdle to using skaware.
The buildManPage structure is kept, instead of building them in a
separate `default.nix`, we add a field `manpages` to
`skawarePackages.buildPackage`, which adds the `"man"` output and
copies everything from the manpages output.
For backwards-compat, the manpage derivation is exposed in the
`passthru` and referenced by the `*-man-pages` attributes.
~~~
The `with skawarePackages;` scope is removed from all packages, and
used explicitly for all functions, while packages get added to the
package import header.
2024-03-04 01:34:38 +01:00
|
|
|
{ skawarePackages, skalibs }:
|
2023-11-09 09:32:29 +01:00
|
|
|
|
skawarePackages: add manpages to their respective packages
For a while now, we’ve had these separate derivations for the skaware
manpages.
That was fine in the beginning, because it was not entirely clear
whether the manpage project would be long-lived. Given that the
collection of third-party manpages is now extensive and updated
regularly, plus it is sanctioned by skarnet, we can remove this
additional hurdle to using skaware.
The buildManPage structure is kept, instead of building them in a
separate `default.nix`, we add a field `manpages` to
`skawarePackages.buildPackage`, which adds the `"man"` output and
copies everything from the manpages output.
For backwards-compat, the manpage derivation is exposed in the
`passthru` and referenced by the `*-man-pages` attributes.
~~~
The `with skawarePackages;` scope is removed from all packages, and
used explicitly for all functions, while packages get added to the
package import header.
2024-03-04 01:34:38 +01:00
|
|
|
skawarePackages.buildPackage {
|
2023-11-09 09:32:29 +01:00
|
|
|
pname = "tipidee";
|
2023-12-21 15:54:26 +01:00
|
|
|
version = "0.0.3.0";
|
|
|
|
|
sha256 = "0dk6k86UKgJ2ioX5H2Xoga9S+SwMy9NFrK2KEKoNxCA=";
|
2023-11-09 09:32:29 +01:00
|
|
|
|
|
|
|
|
description = "A HTTP 1.1 webserver, serving static files and CGI/NPH";
|
|
|
|
|
|
|
|
|
|
outputs = [ "bin" "lib" "out" "dev" "doc" ];
|
|
|
|
|
|
|
|
|
|
configureFlags = [
|
|
|
|
|
"--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-lib=${skalibs.lib}/lib"
|
|
|
|
|
"--with-dynlib=${skalibs.lib}/lib"
|
|
|
|
|
|
|
|
|
|
# we set sysconfdir to /etc here to allow tipidee-config
|
|
|
|
|
# to look in the global paths for its configs.
|
|
|
|
|
# This is not encouraged, but a valid use-case.
|
|
|
|
|
"--sysconfdir=/etc"
|
|
|
|
|
];
|
|
|
|
|
|
|
|
|
|
postInstall = ''
|
|
|
|
|
# remove all tipidee executables from build directory
|
|
|
|
|
rm $(find -type f -mindepth 1 -maxdepth 1 -executable)
|
|
|
|
|
rm libtipidee.*
|
|
|
|
|
|
|
|
|
|
mv doc $doc/share/doc/tipidee/html
|
|
|
|
|
mv examples $doc/share/doc/tipidee/examples
|
|
|
|
|
'';
|
|
|
|
|
|
|
|
|
|
}
|
