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
vscode: Wrap with GAppsHook #45289
vscode: Wrap with GAppsHook #45289
Conversation
@@ -49,8 +49,8 @@ in | |||
}; | |||
|
|||
buildInputs = if stdenv.system == "x86_64-darwin" | |||
then [ unzip makeWrapper libXScrnSaver libsecret ] | |||
else [ makeWrapper libXScrnSaver libxkbfile libsecret ]; | |||
then [ unzip makeWrapper wrapGAppsHook libXScrnSaver libsecret ] |
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.
Darwin probably does not need it. If it is like Atom, they use a different front-end for MacOS.
@jtojnar Okay, is this good? |
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.
Ideally, wrapGAppsHook
would go to nativeBuildInputs
but electron packages are ugly abominations so it probably does not matter.
@@ -50,7 +50,7 @@ in | |||
|
|||
buildInputs = if stdenv.system == "x86_64-darwin" | |||
then [ unzip makeWrapper libXScrnSaver libsecret ] | |||
else [ makeWrapper libXScrnSaver libxkbfile libsecret ]; | |||
else [ makeWrapper wrapGAppsHook libXScrnSaver libxkbfile libsecret ]; |
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.
Why is makeWrapper in the list? To me it looks like it could be removed.
@Mic92 All good? |
Is a backport required here? |
Backport? |
is 18.03 also affected? |
I'm afraid I have no idea, but if the last commit I made to vscode, before this one, is on 18.03, then yes. |
At least for me, #45286 only appeared after the upgrade to vscode 1.26.0. 18.03 is on vscode 1.23.0, so it should be fine. I think we only need to backport this fix if we also upgrade vscode on the release branch. |
Motivation for this change
Fixes #45286
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)