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

vscode: fix #76427 fallout #89196

Merged
merged 3 commits into from Jun 4, 2020
Merged

vscode: fix #76427 fallout #89196

merged 3 commits into from Jun 4, 2020

Conversation

eadwu
Copy link
Member

@eadwu eadwu commented May 30, 2020

Motivation for this change

PR #76427
Original change bb24faf

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@justin-gerhardt
Copy link
Contributor

justin-gerhardt commented May 30, 2020

#76427 seems have undone the changes from bb24faf (It was commited before bb24faf was merged) to vscode-utils.nix but didn't touch pkgs/applications/editors/vscode/with-extensions.nix.
Your commit hardcodes the path as

--add-flags "--extensions-dir ${combinedExtensionsDrv}/share/vscode/extensions"

but "vscode" isn't guaranteed in the current version
installPrefix = "share/${extendedPkgName}/extensions/${vscodeExtUniqueId}";

As far as I can tell reverting the changes from bb24faf wasn't deliberate. Either reapplying bb24faf to update vscode-utils.nix or reverting bb24faf changes to with-extensions.nix seems like a better course of action

@eadwu
Copy link
Member Author

eadwu commented May 30, 2020

I'll keep the share/vscode/extensions since it seems like it's used after the PR.

origin = ''${e}/share/vscode/extensions/${e.vscodeExtUniqueId}'';

Was originally suggested here #71251 (comment).

Though I'll probably eventually(?) take a deeper look to fixup what was added.

@veprbl veprbl linked an issue Jun 4, 2020 that may be closed by this pull request
@veprbl veprbl merged commit dd8f077 into NixOS:master Jun 4, 2020
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.

vscode-with-extensions can't find any extensions
3 participants