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
screenkey: 0.9 -> 1.2 #95437
screenkey: 0.9 -> 1.2 #95437
Conversation
a1adc10
to
0fc2070
Compare
intltool | ||
|
||
file |
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.
What is file
used for?
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.
TBH without it, the build doesn't fail, but it spits:
sh: file: not found
sh: file: not found
sh: file: not found
sh: file: not found
So If you think it'd better without it, tell me.
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.
It would be nice to find out what uses the file so we can document it in the comment.
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 had a slight feeling that it's related to distutils_extra
, and I searched via the web interface at https://bazaar.launchpad.net/~registry/python-distutils-extra/debian/files but I couldn't find any evidence of this to be the cause :/. Perhaps we can hope that my comment mentioning https://gitlab.com/screenkey/screenkey/-/issues/122 is good enough?
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.
OK I added a comment stating that we don't know why file is needed, but without it there are "command not found" errors.
0fc2070
to
494550d
Compare
Forgot to hit the "Comment" button yesterday when writing my comments to your review @jtojnar. |
494550d
to
22554d0
Compare
# This is here and not in buildInputs to avoid scrictDeps issue: | ||
# https://github.com/NixOS/nixpkgs/issues/56943 | ||
gobject-introspection |
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.
It is actually the other way around. It belongs here but causes strictDeps
issues. One way to “fix” it is to move it to buildInputs
as you did before but that is a hack that has its own issues. I prefer disabling strictDeps
instead, which is slightly less hacky.
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 not sure I got to the bottom of this issue, but I moved gobject-introspection
to buildInputs
and disabled strictDeps
.
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 meant that it should remain in nativeBuildInputs
(since that is the correct place) and strictDeps
should be disabled (to bypass the bug).
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 meant that it should remain in nativeBuildInputs (since that is the correct place)
Really? Why?
Also, I didn't experience any issue running screenkey
with either of the options I tested, with and without scrictDeps
set. Still, now everything should be in place as you wish.
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.
We add gobject-introspection
for a setup hook so it should go to nativeBuildInputs
. But that is currently broken with strictDeps = true
(default in Python packages).
f0a7f52
to
5867f2a
Compare
wrapGAppsHook | ||
# https://github.com/NixOS/nixpkgs/issues/56943 |
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.
# https://github.com/NixOS/nixpkgs/issues/56943 | |
# for setup hook |
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.
👍.
- Use Python 3. - Switch to gobject-introspection and other more maintained libraries (vs PyGTK). - Use `fetchFromGitLab`. - Replace the non absolute paths fix in `xlib.py` with `substituteInPlace`.
5867f2a
to
b5caca2
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.
Looks good. Thanks.
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: |
Motivation for this change
Fix #89300 , cc @andys8 .
Things done
(vs PyGTK).
fetchFromGitLab
.xlib.py
withsubstituteInPlace
.cc @rasendubi .
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)