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
ckb/ckb-next: 0.2.9 -> 0.3.2, and cleanup #40043
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Minor changes requested, see the comments. Other than those nitpicks it looks like an approval from me.
I would additionally like if you could add the option rename to the release-notes (nixos/doc/manual/release-notes/rl-1809.xml
). If you can't or don't want to write the release notes just ask and I'll handle it.
b3dca7a
to
d30ff2f
Compare
In this update: * binaries `ckb` and `ckb-daemon` are renamed to `ckb-next` and `ckb-next-daemon` * build system changed from qmake to cmake * the directory searched for animation plugins no longer needs to be patched, as a result of the build system change * modprobe patch has been bumped, since the source repository layout has changed * the cmake scripts are quite FHS-centric and require patching to fix install locations
This changes the description and restart mode to the values present in lib/systemd/system/ckb.service within the ckb package.
The upstream package has officially changed its name to ckb-next.
This avoids leaving the parent shell process (the one executing the unit script) lying around.
This keeps the naming consistent with the other two patches in this directory.
d30ff2f
to
7a0d849
Compare
@samueldr I've pushed an updated version of this PR. Changes are:
P.S. Github's UI appears to be behaving weirdly for me: on some page loads, the head commit of |
nixos/modules/hardware/ckb-next.nix
Outdated
imports = [ | ||
(mkRenamedOptionModule ["hardware" "ckb" "enable"] ["hardware" "ckb-next" "enable"]) | ||
(mkRenamedOptionModule ["hardware" "ckb" "package"] ["hardware" "ckb-next" "package"]) | ||
]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, looks like I missed those renames. I personally don't mind if those are kept local to the relevant module, but it looks like most renames are in nixos/modules/rename.nix
.
I wouldn't hold back the change on account of that, though let's say what you yourself think about it, and if others have a strong opinion about that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm thinking it would be more consistent to put them in nixos/modules/rename.nix
. I feel it makes sense for that file to be the first port of call when (if?) deprecated aliases for options are eventually cleaned up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than the really nit-picky comment, and the merge conflict, this looks fine. Everything fixed as asked.
@samueldr Thanks for the review! I've fixed the merge conflict and moved the option renames as suggested. |
Thanks! |
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)