As mentioned several times earlier, there’s no difference, hence there’s no reason to put this explanation in the manual*; the manual’s bloated due to scope creep, and therefore overwhelming as is.
*ETA: this is just my opinion, anyway.
Hard disagree. If it’s one and the same, that fact should absolutely be documented.
I don’t find the manual to be bloated or overwhelming in any way content wise. The biggest issue I have with it is that it’s not really searchable.
I’d want something that has the contents of the Nixpkgs manual but presented like the Arch wiki with a similar separation of articles.
4 Likes
“Consumer” is largely undefined here (and I’d argue that in some respects that’s even a good thing, although clearly not always), ergo the “nixpkgs as a library and buildPythonPackage as part of the public interface” alternative, but I think this conversation has already happened somewhere else on the forum