while this could be considered a change in digga's api, flake-utils-plus
wouldn't allow duplicate hostnames either, because its `hosts` option
does not separate nixos or darwin hosts -- both live at `hosts.<hostname>`.
439: Remove suites, profiles, and old importer code r=blaggacao a=Pacman99
I'm keeping the deprecation code for `externalModules` still, since there hasn't been a proper release that included that code.
Co-authored-by: Parthiv Seetharaman <pachum99@myrdd.info>
The divnix fork paches don't actually matter because we always pass fup
a channel input. Digga will error out early if there is any issues, so
fup channel input auto-detection never gets called.
This experimental feature has been removed from Nix in unstable
versions recently, and with this set, it now pops up an unsupressable
warning message. Not so bad on its own, but when using <kbd>Tab</kbd>
completion it corrupts the output.
now that we have per-host custom tests, it does not make sense anymore
to have magic lumpsum tests.
users are encouraged to use the new digga.lib.allProfilesTest standard
test and add it to a host's test like so:
`nixos.<host>.tests = [ digga.lib.allPrefilesTest ];`
Users may not have setup their nix correctly. This ensures they have the
proper features and caches setup when they use this repo.
We currently have not entire clarity wether all `nixConig` flake options
work. At some point in time `nix` support was limited.
Therefore, we implement an NIX_CONFIG fallback (at least) in the devshell
supersedes #69
It is very likely that some digga functionality requires patches to nix
Create a place for patches that mimicks the way how they could be
applied once `inputs.<name>.patches` of the
UFR (Unofficial Flakes Roadmap) is implemented.
Also showcase how `nixConfig` can add extra feature flags (without
overriding the patched-in ones).
in order to avoid people accidentially depending on some internal API
which we don't explicitly want to support well into version 1.0, hide
those from the output.
Users who still want to use those need to copy them over, instead.
This reduces our API exposure and hopefully will help save maintainer
resources once `digga` completely takes over the world.
