From d4963a3a58bd6364c90735f201ab8a88ef0d28aa Mon Sep 17 00:00:00 2001 From: Gavin John Date: Tue, 15 Jul 2025 11:27:25 -0400 Subject: [PATCH] pkgs/README: Clarify library dependent incluson criterion --- pkgs/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/pkgs/README.md b/pkgs/README.md index 83d264d95085..f617a0016317 100644 --- a/pkgs/README.md +++ b/pkgs/README.md @@ -38,7 +38,9 @@ Before adding a new package, please consider the following questions: * How realistic is it that it will be used by other people? It's good that nixpkgs caters to various niches, but if it's a niche of 5 people it's probably too small. A good estimate is checking upstream issues and pull requests, or other software repositories. - Library packages should have at least one dependent. + * Library packages should have at least one dependent. + If possible, that dependent should be packaged in the same PR the library is added in, as a sanity check. + If it is not possible to package the dependent, a minimal test program should be added to `passthru.tests`. * Is the software actively maintained upstream? Especially packages that are security-critical, rely on fast-moving dependencies, or affect data integrity should see regular maintenance. * Are you willing to maintain the package?