You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My main configuration file is /etc/nixox/configuration.nix, however, I keep my environment.systemPackages in aroun.nix and have import in configuration.nix via
imports =
[ # Include the results of the hardware scan.
./hardware-configuration.nix
./aroun.nix
];
If the sofware-center parser could open the files under imports, parse them, and find the location of environment.systemPackages, that would be great
May not be exactly what you're looking for, but if you have a specific file containing environment.systemPackages that you want the software center to use, selecting that instead of configuration.nix in the preferences should work. But parsing imports is definitely something that would greatly expand configuration flexibility using this program!
Yes, for now I just point to the file where I have most of my systemPackages, and that works fine for me. As per the NixOS manual, it is possible to have multiple definitions of the same option, see https://nixos.org/manual/nixos/stable/index.html#sec-modularity.
Note that both configuration.nix and kde.nix define the option environment.systemPackages. When multiple modules define an option, NixOS will try to merge the definitions. In the case of environment.systemPackages, that’s easy: the lists of packages can simply be concatenated. The value in configuration.nix is merged last, so for list-type options, it will appear at the end of the merged list. If you want it to appear first, you can use mkBefore.
My main configuration file is /etc/nixox/configuration.nix, however, I keep my
environment.systemPackages
in aroun.nix and have import in configuration.nix viaIf the sofware-center parser could open the files under
imports
, parse them, and find the location of environment.systemPackages, that would be greatcf. snowfallorg/nixos-conf-editor#7
The text was updated successfully, but these errors were encountered: