6 commits

Author	SHA1	Message	Date
Profpatsch	7cadc17591	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-24 14:52:19 +01:00
Alyssa Ross	cd59bf343f	execline: 2.9.3.0 -> 2.9.4.0	2023-11-07 13:05:31 +00:00
Alyssa Ross	82e832bbf2	execline: 2.9.1.0 -> 2.9.3.0	2023-04-06 09:46:35 +00:00
Alyssa Ross	3b215117a2	execline: man pages: 2.9.0.0.1 -> 2.9.1.0.1	2023-01-17 19:21:00 +00:00
Alyssa Ross	2bcc676d41	execline: 2.9.0.1 -> 2.9.1.0	2023-01-17 19:21:00 +00:00
AndersonTorres	a76bd55090	skawarePackages: move all of them to development/skaware-packages	2022-10-28 11:30:49 -03:00