nixos/rl-2211: remove reference to nowhere
The note this originally referred to was moved to the “Internal Changes” section and later trimmed down, so the referenced content is no longer there.
This commit is contained in:
parent
b22e868d22
commit
2a04723331
|
@ -314,10 +314,7 @@
|
|||
generated using <literal>lib.systems.elaborate</literal>. In
|
||||
most cases you will want to use the new
|
||||
<literal>canExecute</literal> predicate instead which also
|
||||
considers the kernel / syscall interface. It is briefly
|
||||
described in the release’s
|
||||
<link linkend="sec-release-22.11-highlights">highlights
|
||||
section</link>.
|
||||
takes the kernel / syscall interface into account.
|
||||
<literal>lib.systems.parse.isCompatible</literal> still
|
||||
exists, but has changed semantically: Architectures with
|
||||
differing endianness modes are <emphasis>no longer considered
|
||||
|
|
|
@ -90,8 +90,7 @@ In addition to numerous new and upgraded packages, this release includes the fol
|
|||
- The `isCompatible` predicate checking CPU compatibility is no longer exposed
|
||||
by the platform sets generated using `lib.systems.elaborate`. In most cases
|
||||
you will want to use the new `canExecute` predicate instead which also
|
||||
considers the kernel / syscall interface. It is briefly described in the
|
||||
release's [highlights section](#sec-release-22.11-highlights).
|
||||
takes the kernel / syscall interface into account.
|
||||
`lib.systems.parse.isCompatible` still exists, but has changed semantically:
|
||||
Architectures with differing endianness modes are *no longer considered compatible*.
|
||||
|
||||
|
|
Loading…
Reference in a new issue