-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
mouse-actions: init at 0.4.4 #265056
mouse-actions: init at 0.4.4 #265056
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 for contributing to nixpkgs!
Alright thanks for the criticism! ^-^ I think I've resolved everything so far. However not too sure how I should organize my commits, is it ok for there to be so many? Specifically the last one which moves and renames |
1 for the maintainer and 1 for the package would be ideal 👍 |
b3c3409
to
63ae3c1
Compare
Alright, I think I've done it. |
Result of 1 package failed to build:
I got it to run after changing [2023-11-02T19:16:00Z ERROR mouse_actions::process_args] Grab Error: IoError(
Os {
code: 13,
kind: PermissionDenied,
message: "Permission denied",
},
)
[2023-11-02T19:16:00Z ERROR mouse_actions::process_args] The user must be in the file group of /dev/input files, usually 'input' or 'plugdev' :
[2023-11-02T19:16:00Z ERROR mouse_actions::process_args] $ sudo usermod -a -G input $USER
[2023-11-02T19:16:00Z ERROR mouse_actions::process_args] $ sudo usermod -a -G plugdev $USER
[2023-11-02T19:16:00Z ERROR mouse_actions::process_args] $ sudo tee /etc/udev/rules.d/80-mouse-actions.rules <<<'KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess", OPTIONS+="static_node=uinput"'
[2023-11-02T19:16:00Z ERROR mouse_actions::process_args] Then restart to apply this user modifications.
[2023-11-02T19:16:00Z ERROR mouse_actions::process_args] See https://github.com/jersou/mouse-actions#requirement- |
I wasn't sure how to do this either. The upstream doesn't give any solution besides just |
Unfortunately I can't approve since I'm unfamiliar with how to proceed from here. Maybe someone else can help out. |
can you squash your commits from the review, ideally there should only be 2 commits |
Usually a |
fc17138
to
4d0c175
Compare
Alright, I'll look into this tomorrow morning. Would this mean that it technically doesn't work on distros which aren't NixOS, and I should update |
4d0c175
to
ecb9d5a
Compare
The package itself can be run on other distros, the user then just needs to set their groups and udev rules manually. Besides that I don't think it's possible to exclude other distros using |
985e773
to
71717ff
Compare
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/prs-already-reviewed/2617/1209 |
Anything I can do at this point to help get this merged? |
I also would like this merged, is there something missing? |
71717ff
to
b3591da
Compare
019e635
to
24f8269
Compare
a69ca8a
to
e94b24e
Compare
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.
second commit msg can be cleaned up to just one line, otherwise lgtm
I removed the squashed messages, but am leaving the "Co-authored by [...]" lines. Is that OK? |
e94b24e
to
980a8d0
Compare
Co-authored-by: Donovan Glover <[email protected]> Co-authored-by: Arne Keller <[email protected]>
980a8d0
to
28614f6
Compare
Yes, that is how it is supposed to be done. |
Description of changes
https://github.com/jersou/mouse-actions
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)