b0d3044823
We should only make use of asserts to assert a property about the *current* attribute in order to make it possible for downstream users to change versions of packages: When a downstream user changes the package an attribute points to, the assert is removed as the attribute is swapped out, so asserting something about itself is okay. However, when it asserts a property about another package, changing that other package may break the package unexpectedly, with no better workaround then passing in an empty `configurationCommon` overlay. See also: https://github.com/NixOS/nixpkgs/pull/166425 |
||
---|---|---|
.. | ||
androidndk-pkgs | ||
beam-modules | ||
bower-modules/generic | ||
chez-modules | ||
compilers | ||
coq-modules | ||
dhall-modules | ||
dotnet-modules | ||
em-modules/generic | ||
embedded | ||
gnuradio-modules | ||
go-modules | ||
go-packages | ||
guile-modules | ||
haskell-modules | ||
idris-modules | ||
interpreters | ||
java-modules | ||
libraries | ||
lisp-modules | ||
lua-modules | ||
misc | ||
mobile | ||
nim-packages | ||
node-packages | ||
ocaml-modules | ||
octave-modules | ||
perl-modules | ||
pharo | ||
php-packages | ||
pure-modules | ||
python2-modules | ||
python-modules | ||
quickemu | ||
r-modules | ||
ruby-modules | ||
scheme-modules/scheme-bytestructures | ||
tools | ||
web |