summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorBas van Dijk <v.dijk.bas@gmail.com>2020-04-20 23:53:31 +0200
committerBas van Dijk <v.dijk.bas@gmail.com>2020-07-20 13:44:18 +0200
commitd06de760f8f4a3c304addb33c372d706cc6c6c9e (patch)
tree7a0a6fc9ffe1daf182129f538e5535f76686d6a3 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent27296cc5c572da9a7ba35638a139a168a301ee14 (diff)
nixos/modules/system/activation/top-level.nix: allow overriding system.name
The toplevel derivations of systems that have `networking.hostName` set to `""` (because they want their hostname to be set by DHCP) used to be all named `nixos-system-unnamed-${config.system.nixos.label}`. This makes them hard to distinguish. A similar problem existed in NixOS tests where `vmName` is used in the `testScript` to refer to the VM. It defaulted to the `networking.hostName` which when set to `""` won't allow you to refer to the machine from the `testScript`. This commit makes the `system.name` configurable. It still defaults to: ``` if config.networking.hostName == "" then "unnamed" else config.networking.hostName; ``` but in case `networking.hostName` needs to be to `""` the `system.name` can be set to a distinguishable name.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions