vscode-extensions-update: init#389585
Conversation
|
Hello, I'm glad to see this issue being worked on. I haven't yet carefully check your script but here are a few suggestions:
You can find a script I use regularly to update the VSCode extension here. |
drupol
left a comment
There was a problem hiding this comment.
I left a few minor comments.
I have more important questions now:
- I see you're doing a lot of processing to manually update the hash with the updated one. There are tools that do that already. Wouldn't it be better to use those tools instead of reinventing them?
- How do you handle extensions that have multiple hashes based on their system ? I have the feeling that this is not covered by the script.
- How is the script meant to be used? I don't really understand how to run it.
Thanks!
pkgs/by-name/vs/vscode-extensions-update-script/vscode_extensions_update.py
Outdated
Show resolved
Hide resolved
pkgs/by-name/vs/vscode-extensions-update-script/vscode_extensions_update.py
Outdated
Show resolved
Hide resolved
pkgs/by-name/vs/vscode-extensions-update-script/vscode_extensions_update.py
Outdated
Show resolved
Hide resolved
pkgs/by-name/vs/vscode-extensions-update-script/vscode_extensions_update.py
Outdated
Show resolved
Hide resolved
pkgs/by-name/vs/vscode-extensions-update/vscode_extensions_update.py
Outdated
Show resolved
Hide resolved
pkgs/by-name/vs/vscode-extensions-update/vscode_extensions_update.py
Outdated
Show resolved
Hide resolved
This comment was marked as resolved.
This comment was marked as resolved.
pkgs/by-name/vs/vscode-extensions-update/vscode_extensions_update.py
Outdated
Show resolved
Hide resolved
pkgs/by-name/vs/vscode-extensions-update/vscode_extensions_update.py
Outdated
Show resolved
Hide resolved
pkgs/by-name/vs/vscode-extensions-update/vscode_extensions_update.py
Outdated
Show resolved
Hide resolved
pkgs/by-name/vs/vscode-extensions-update/vscode_extensions_update.py
Outdated
Show resolved
Hide resolved
pkgs/applications/editors/vscode/extensions/ms-python.python/default.nix
Outdated
Show resolved
Hide resolved
jraygauthier
left a comment
There was a problem hiding this comment.
Haven't reviewed the update script itself but this is a really nice centralization of the update scripts, it removes a lot of complexity from packages. Good job.
There was a problem hiding this comment.
Shouldn't we add the updater by default in this builder ?
There was a problem hiding this comment.
Yep, with the option to override.
There was a problem hiding this comment.
Sorry, I meant that we should be able to override passthru.updateScript in extensions when we want.
I think we can add it here.
There was a problem hiding this comment.
If I were to vote, I'd vote for updating them individually, without using any kind of json file.
There was a problem hiding this comment.
To be honest, I am in favor of updating all of them in one go, periodically, while still allowing updates of individual extensions. vscode-extensions maintenance is the second worst on Nixpkgs, after kernel modules.
Provided we account for bugs like these of course. (#392786)
There was a problem hiding this comment.
How about merging this today, are you all OK with that? I think the script is great and is going to help a lot until we perhaps have another solution that you mentionned.
There was a problem hiding this comment.
Sadly I don't think this will be ever possible.
There was a problem hiding this comment.
Let's merge this today, and maybe try to reimplement the extensions structure to use a versions.json later. @emaryn you okay with that?
JohnRTitor
left a comment
There was a problem hiding this comment.
nixpkgs-vet check needs a fix perhaps
|
I'm thinking about something, would it be a good idea to add this script to all the extensions that have their own file (namely, those that are not defined in |
|
I'm trying to update the vscode extension, I added `meta.platforms set to: The command I run is: But it only update the |
There's no sorry needed here :) Do you plan to do an update PR? If yes, WDYT about using the method |
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.