When I look for example at this file:
It calls source files via
pkgs.callPackage and a globally scoped
pkgs only for the reason that fetchers (the only attributes supposedly ever used in source files) do not have a separate handle / scope.
This is confusing since it suggests the necessity of this global scope when calling
file and hides away the reality that only the hypothetical
fetch* interface is used.
If I had to coin it, I would probably call it a deceptive scope mismatch ?
Has the community already found a coining for the necessity of this convoluted arrangement?
I’m looking for a somewhat generally accepted name to be able to mentally isolate it as a “historic glitch” when reasoning about folder hierarchies and scopes.
This is somewhat relevant when looking at nix code as trying to be self-documenting, because an inattentive (inexperienced) reader would tend to imply that nixpkgs version is important and could break things down within this sub folder tree. But the reality is, only changes to the quite stable hypothetical fetcher* interface could break things, the nixpkgs version can thus be largely arbitrary (within those constraints). Hence, there is no real dependence on