You can do a nixos-rebuild test or a nix-build - A system. Either way you have to make sure it's using your own nixpkgs/nixos.
Then you can look at the resulting cron job in the result. On Jun 16, 2014 6:57 AM, "Mateusz Kowalczyk" <fuuze...@fuuzetsu.co.uk> wrote: > Greetings, > > I just opened [1] and started to implement it, basically making > pass-through options that user can configure. > > What is the way to test NixOS modules? I don't particularly want to wait > until ‘updatedb’ is scheduled to run, perhaps I only want to see the > final command nix produces. I don't particularly want to install > half-finished and experimental changes onto my system either. With nix > packages I can nix-build and then play with the results but is there > anything of the sort for system modules? > > Another question is whether I should be trying to catch obvious mistakes > and how: say there's on option that takes a username. In order to do > something sensible, the user has to exist. Should I be checking for this > and throwing an error when the user doesn't exist on the system or are > we trusting the user to know it best and to configure it all properly. > If some checks are in order, how do we throw an error? ‘assert’? > > [1]: https://github.com/NixOS/nixpkgs/issues/2961 > -- > Mateusz K. > _______________________________________________ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev >
_______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
