Skip to content

Removed networking.fqdn option #27798

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 31, 2017
Merged

Removed networking.fqdn option #27798

merged 1 commit into from
Jul 31, 2017

Conversation

regellosigkeitsaxiom
Copy link
Contributor

@regellosigkeitsaxiom regellosigkeitsaxiom commented Jul 31, 2017

Motivation for this change

Adding it was a mistake which can only lead to problems and confusion.
A cleanup after #27105. See discussion with @edolstra in #27105 for details.

Things done

Please check what applies. Note that these are not hard requirements but merely serve as information for reviewers.

  • Tested using sandboxing
    (nix.useSandbox on NixOS,
    or option build-use-sandbox in nix.conf
    on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • Linux
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

Sorry, something went wrong.

Adding it was a mistake which can only lead to problems and confusion.
@globin globin merged commit d30b2eb into NixOS:master Jul 31, 2017
@Ma27
Copy link
Member

Ma27 commented Jul 31, 2017

this change misses an entry in rename.nix which might lead to confusion if a build breaks

@regellosigkeitsaxiom
Copy link
Contributor Author

@Ma27 something like this?

Option existed for only couple of days, I am not sure if it really needs to leave such traces.

@edolstra
Copy link
Member

Indeed we don't have to provide backwards compatibility for options that only existed on master (regardless of the length of time).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants