From 6f2be7c0951f7c975000fed96431feae17eba3e6 Mon Sep 17 00:00:00 2001 From: Silvan Mosberger Date: Wed, 6 Dec 2023 23:15:06 +0100 Subject: [PATCH] pkgs/by-name: Mention possibility of avoiding alternate callPackage's This is preferred over using the category hierarchy Co-authored-by: Anderson Torres --- pkgs/by-name/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/pkgs/by-name/README.md b/pkgs/by-name/README.md index fbb8b0dc05c1..a7cdc57201df 100644 --- a/pkgs/by-name/README.md +++ b/pkgs/by-name/README.md @@ -99,7 +99,9 @@ There's some limitations as to which packages can be defined using this structur - Only packages defined using `pkgs.callPackage`. This excludes packages defined using `pkgs.python3Packages.callPackage ...`. - Instead use the [category hierarchy](../README.md#category-hierarchy) for such attributes. + Instead: + - Either change the package definition to work with `pkgs.callPackage`. + - Or use the [category hierarchy](../README.md#category-hierarchy). - Only top-level packages. This excludes packages for other package sets like `pkgs.pythonPackages.*`.