Skip to content
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

trust-dns: rebrand as hickory-dns #262268

Closed
wants to merge 1 commit into from

Conversation

oneingan
Copy link
Contributor

Description of changes

Trust DNS project has been recently rebranded to Hickory DNS. This blog post explains the reasoning behind this move.

I have staged more changes to Hickory DNS package and NixOS Module but prefer for this PR only cover the rebranding stuff.

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 23.11 Release Notes (or backporting 23.05 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

@nixos-discourse
Copy link

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/prs-ready-for-review/3032/2784

serviceConfig = {
ExecStart =
let
flags = (lib.optional cfg.debug "--debug") ++ (lib.optional cfg.quiet "--quiet");
flagsStr = builtins.concatStringsSep " " flags;
in ''
${cfg.package}/bin/trust-dns --config ${configFile} ${flagsStr}
${cfg.package}/bin/hickory-dns --config ${configFile} ${flagsStr}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

without bumping the package version, this change doesn't work. 0.23.0 still ships only bin/trust-dns and not bin/hickory-dns. and 0.24.0 ships bin/hickory-dns only, without bin/trust-dns. so unless we want to introduce and leverage meta.mainProgram, there has to be a patch which simultaneously upgrades 0.23.0 -> 0.24.0 and changes the name here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here's a PR which, if merged before the rebrand, would address this issue: #263054

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR above has been merged, should be safe to just leave this line as it's set in master

@uninsane uninsane mentioned this pull request Oct 24, 2023
13 tasks
@uninsane
Copy link
Contributor

uninsane commented Nov 9, 2023

@oneingan if you get a chance to rebase this patch, it should be good to go. i can give it a deploy and then sign off.

@SuperSandro2000
Copy link
Member

@oneingan can you please rebase the PR?

@oneingan
Copy link
Contributor Author

oneingan commented Jan 1, 2024

Apologies for the wait. The situation is that initially, we intended to implement trust-dns in our company, but we opted for a different solution. If you're still comfortable with it, I can attempt to merge this, but please note that I may not be able to provide ongoing maintenance for it.

@uninsane
Copy link
Contributor

uninsane commented Jan 1, 2024

please note that I may not be able to provide ongoing maintenance for it.

i'm committed to maintaining trust-dns/hickory-dns for the indefinite future, so no problem there. if you're still using trust-dns in a more limited context or otherwise want to provide review/testing on future package updates, that's more than okay, otherwise just remove your name from maintainers = [ colinsane juaningan ] when doing the rebase and don't worry about it :)

@aktaboot
Copy link
Contributor

would be nice to have this merged, if there isn't much blocking it

@uninsane uninsane mentioned this pull request Jun 1, 2024
13 tasks
@uninsane
Copy link
Contributor

uninsane commented Jun 1, 2024

rebased and resurrected as a new PR since i don't have permissions to update this one. i've kept @oneingan as the commit author.

@uninsane uninsane closed this Jun 1, 2024
@oneingan oneingan deleted the rebrand-trust-dns branch June 2, 2024 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants