Closed Shados closed 1 year ago
Interesting, so this happens because: By including all modules for the manual, you're also including the configuration.nix
where you have the disabledModules
, which means it won't be available for the manual build.
I think the best solution would be to provide an option for toggling validity checks, enabled by default.
I marked this as stale due to inactivity. → More info
Still matters to me.
I marked this as stale due to inactivity. → More info
Still matters to me.
@Shados is it still an issue?
I just checked, and: nope (or at least not for the case I ran into the issue in), it appears this was resolved at some point.
Describe the bug
disabledModules
usage can cause NixOS manual build failures in combination withdocumentation.nixos.includeAllModules
being enabled.To Reproduce Steps to reproduce the behavior:
disabledModules
to disable a module that is referenced by one of the hand-written portions of the NixOS manual (like the release notes). Example:disabledModules = [ "services/networking/dnscrypt-proxy2.nix" ];
, which has references to its options fromnixos/doc/manual/release-notes/rl-2003.xml
.documentation.nixos.includeAllModules = true
.nixos-rebuild
, watch it fail to build the NixOS manual due to a dangling reference.Expected behavior Personally, I find having my local modules included in locally built versions of the manual more useful than having links/references to modules from hand-written portions of the manual, so I'd expect the build to succeed (possibly with a warning about missing references).
On the flip side, I can see this is very much an edge case, and other people may prefer the current behaviour. Although it will likely mean incidental manual breakages down the line when module options change without the hand-written portions of the manual altering to match.
Notify maintainers @Infinisil ?
Metadata