VSCodium snap package? #1466

Originally created by @amankkg on GitHub.

The recent release of VSCode v. 1.33 is now distributed via snap package https://snapcraft.io/code

Would be great to see a snap package for this project also!

Originally created by @amankkg on GitHub. The recent release of VSCode v. 1.33 is now distributed via snap package https://snapcraft.io/code Would be great to see a snap package for this project also!

giteasync added the help wanted label 2025-09-10 23:53:10 -05:00

giteasync closed this issue

giteasync commented

@darkdecoy commented on GitHub:

We could but it will need to be tweaked

@darkdecoy commented on GitHub: We could but it will need to be tweaked

giteasync commented

@eaglersdeveloper commented on GitHub:

VS Code already has snapcraft.yaml. What if we will use it?

@eaglersdeveloper commented on GitHub: VS Code already has [snapcraft.yaml](https://github.com/Microsoft/vscode/blob/master/resources/linux/snap/snapcraft.yaml). What if we will use it?

giteasync commented

@stripedpajamas commented on GitHub:

Sure!

@stripedpajamas commented on GitHub: Sure!

giteasync commented

@stripedpajamas commented on GitHub:

I think this is important for us to get working, as the goal would be 100% parity with what is offered by Microsoft. Any help is appreciated toward this goal; I will look into it also when I have some time to.

@stripedpajamas commented on GitHub: I think this is important for us to get working, as the goal would be 100% parity with what is offered by Microsoft. Any help is appreciated toward this goal; I will look into it also when I have some time to.

giteasync commented

@darkdecoy commented on GitHub:

I would be interested in helping if you are still looking for someone to help with this

@darkdecoy commented on GitHub: I would be interested in helping if you are still looking for someone to help with this

giteasync commented

@zicklag commented on GitHub:

Who build it?

It looks like it may have been built from here: https://github.com/ErnyTech/vscodium.snap

@zicklag commented on GitHub: > Who build it? It looks like it may have been built from here: https://github.com/ErnyTech/vscodium.snap

giteasync commented

@bittner commented on GitHub:

There was a vscodium in the "edge" channel for snaps (i.e. automatically built off source). What is the status on this?

Currently, what you get when trying to install vscodium is:

$ snap install vscodium
error: snap "vscodium" is not available on this architecture (amd64) but exists on other
       architectures (i386).

@bittner commented on GitHub: There was a `vscodium` in the "edge" channel for snaps (i.e. automatically built off source). What is the status on this? Currently, what you get when trying to install vscodium is: ```console $ snap install vscodium error: snap "vscodium" is not available on this architecture (amd64) but exists on other architectures (i386). ```

giteasync commented

@impredicative commented on GitHub:

Sorry but is there any status update for this issue? snap installation will make VSCodium a lot more attractive IMHO.

@impredicative commented on GitHub: Sorry but is there any status update for this issue? snap installation will make VSCodium a lot more attractive IMHO.

giteasync commented

@AktasC commented on GitHub:

I'm gonna try to build this for Solus by the end of the month, since the snap package won't come quicker anyway, have a lot of work going on currently.

If you have any suggestions feel free to ping me here.

@AktasC commented on GitHub: I'm gonna try to build this for Solus by the end of the month, since the snap package won't come quicker anyway, have a lot of work going on currently. If you have any suggestions feel free to ping me here.

giteasync commented

@eaglersdeveloper commented on GitHub:

Who build it?

@eaglersdeveloper commented on GitHub: Who build it?

giteasync commented

@hellsworth commented on GitHub:

It is unlikely that Canonical will take up snapping vscodium for two reasons:

A user already is providing this in the snap store
Canonical has worked with Microsoft to provide vscode in the snap store

The best thing to do would be to get the person that published vscodium in the snap store, to transfer the project to be part of snapcrafters, which is a community that maintains snaps.

@hellsworth commented on GitHub: It is unlikely that Canonical will take up snapping vscodium for two reasons: 1. A user already is providing this in the snap store 2. Canonical has worked with Microsoft to provide [vscode in the snap store](https://snapcraft.io/code) The best thing to do would be to get the person that published vscodium in the snap store, to transfer the project to be part of [snapcrafters](https://github.com/snapcrafters), which is a community that maintains snaps.

giteasync commented

@hackel commented on GitHub:

This needs to become the default (and only) version of VSCode available in the Snap Store. They do a terrible job of warning users about telemetry/spyware.

@hackel commented on GitHub: This needs to become the default (and only) version of VSCode available in the Snap Store. They do a terrible job of warning users about telemetry/spyware.

giteasync commented

@stripedpajamas commented on GitHub:

@bittner @hellsworth -- I think I'm actually the one who "owns" the vscodium snap. Someone made it initially and then transferred to me. I haven't gotten any time to figure out making the snap hence it has gone stale.

I'm very uninformed when it comes to snaps. What is the best path forward-- what happens if I were to transfer to snapcrafters?

@stripedpajamas commented on GitHub: @bittner @hellsworth -- I think I'm actually the one who "owns" the vscodium snap. Someone made it initially and then transferred to me. I haven't gotten any time to figure out making the snap hence it has gone stale. I'm very uninformed when it comes to snaps. What is the best path forward-- what happens if I were to transfer to snapcrafters?

giteasync commented

@ghost commented on GitHub:

@hellsworth is it possible canoncial (beside cherrytree) snapifies vscodium which would be extremly popular (with many privacy concernd users)?

@ghost commented on GitHub: @hellsworth is it possible canoncial (beside cherrytree) snapifies vscodium which would be extremly popular (with many privacy concernd users)?

giteasync commented

@bittner commented on GitHub:

@hellsworth With 1. above, do you refer to https://snapcraft.io/vscodium?

Interestingly, this snap is not listed with snap search, not sure why. I couldn't see any author information otherwise, so I asked Canonical for support via the "Report this app" link at the bottom of the page.

Now cross your fingers and wait! 🤞

@bittner commented on GitHub: @hellsworth With 1. above, do you refer to https://snapcraft.io/vscodium? Interestingly, this snap is not listed with `snap search`, not sure why. I couldn't see any author information otherwise, so I asked Canonical for support via the "Report this app" link at the bottom of the page. Now cross your fingers and wait! :crossed_fingers:

giteasync commented

@stripedpajamas commented on GitHub:

I see https://snapcraft.io/codium -- does this issue need to remain open?

@stripedpajamas commented on GitHub: I see https://snapcraft.io/codium -- does this issue need to remain open?

giteasync commented

@zicklag commented on GitHub:

@bittner I'm pretty sure the reason it is not listed in search is because the snap only has an "edge" release. If we made a stable release it would show in searches.

@zicklag commented on GitHub: @bittner I'm pretty sure the reason it is not listed in search is because the snap only has an "edge" release. If we made a stable release it would show in searches.

giteasync commented

@bittner commented on GitHub:

The project is called "VSCodium" (just like "VSCode" is called VS Code),
The binary is meant to be called "codium" (just like "code" is called, w/o the leading "vs").
The packages (and packagers) on the various platforms do whatever they want. (Hey, it's free software! Let us do what we want! 🙄 😆)

See #28 and #36 for a bit of history.

P.S.: Say hello to Marc Shuttleworth, my hero! 😍

@bittner commented on GitHub: - The project is called "VSCodium" (just like "VSCode" is called VS Code), - The binary is meant to be called "codium" (just like "code" is called, w/o the leading "vs"). - The packages (and packagers) on the various platforms do whatever they want. (Hey, it's free software! Let us do what we want! :roll_eyes: :laughing:) See #28 and #36 for a bit of history. P.S.: Say hello to Marc Shuttleworth, my hero! :heart_eyes:

giteasync commented

@popey commented on GitHub:

Ok, just built an up to date VSCodium snap.

Aside: Is it VSCodium, or Codium? Because there appears to be a split personality going on in the releases area on github :D.

Where does this yaml need to live? I could contribute it as a PR to this repo and then someone from the {VS}Codium team could own the snap going forward? If upstream {VS}Codium don't want to maintain the snap, it could go in snapcrafters, but we'd rather upstreams maintained their snaps, as a goal.

Let me know what you want to do.

@popey commented on GitHub: ![Screenshot from 2020-02-11 21-00-34](https://user-images.githubusercontent.com/1841272/74279163-4e804280-4d12-11ea-9635-39dbfbdfa1ff.png) Ok, just built an up to date VSCodium snap. Aside: _Is it VSCodium, or Codium? Because there appears to be a split personality going on in the releases area on github :D._ Where does this yaml need to live? I could contribute it as a PR to this repo and then someone from the {VS}Codium team could own the snap going forward? If upstream {VS}Codium don't want to maintain the snap, it could go in snapcrafters, but we'd rather upstreams maintained their snaps, as a goal. Let me know what you want to do.

giteasync commented

@popey commented on GitHub:

@bittner actually it doesn't show because there is only an i386 build in edge. There's no AMD64 build in any channel.

@popey commented on GitHub: @bittner actually it doesn't show because there is only an i386 build in edge. There's no AMD64 build in any channel.

giteasync commented

@jobukkit commented on GitHub:

If you search for "vscodium" on Snapcraft without the space, you get an old version.

@jobukkit commented on GitHub: If you search for "vscodium" on Snapcraft without the space, you get an old version.

giteasync commented

@amankkg commented on GitHub:

cool, closing then

@amankkg commented on GitHub: cool, closing then

giteasync commented