Package Details: vscodium-git 1.95.1.24307.r5.gd598450-1

Git Clone URL: https://aur.archlinux.org/vscodium-git.git (read-only, click to copy)
Package Base: vscodium-git
Description: Free/Libre Open Source Software Binaries of VSCode (git build from latest commit).
Upstream URL: https://github.com/VSCodium/vscodium.git
Licenses: MIT
Conflicts: codium, vscodium, vscodium-bin, vscodium-git
Provides: codium, vscodium
Submitter: Salamandar
Maintainer: cedricroijakkers (daiyam)
Last Packager: daiyam
Votes: 7
Popularity: 0.21
First Submitted: 2020-03-24 09:33 (UTC)
Last Updated: 2024-11-05 16:40 (UTC)

Pinned Comments

cedricroijakkers commented on 2022-09-05 10:42 (UTC)

NOTE: If you are building in a chroot, make sure package systemd-sysvcompat is installed on your system, as this is required for nvm. This cannot be included in the dependencies, since it will break on non-systemd distributions.

cedricroijakkers commented on 2021-04-10 15:26 (UTC)

This package is now the git build of the very latest commit on the VSCodium branch. If you wish to use the latest released version, switch to the vscodium package.

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

cedricroijakkers commented on 2021-05-20 06:12 (UTC) (edited on 2021-05-20 06:13 (UTC) by cedricroijakkers)

What @slimb says actually already happened a few times. I've tried tracking the master branch of vscodium and the main branch of vscode, but that would regularly break since Microsoft would make changes that are not fixed in vscodium yet.

This is why I'm using the same script the vscodium build is using to determine which tag of vscode to check out, but this needs to happen at build time, I cannot simply do this at source=() time, making this build tricky, and pkgver() not update automatically in the AUR.

I think the only thing I can do is set up a CI that tracks the vscodium master branch, executes the build and pushes the update to the AUR git repo.

FuzzyMidnight commented on 2021-05-20 05:56 (UTC)

@MithicSpirit wouldn't it be safer to just wait for vscodium to update incase vscode has breaking change?

MithicSpirit commented on 2021-05-20 02:37 (UTC)

@cedricroijakkers you could try checking other package's pkgver(). The only difference this one should have to most other -git packages is to mark both the vscodium commit and the vscode commit in the version imo.

cedricroijakkers commented on 2021-05-19 07:15 (UTC)

Interesting. I've bumped the version manually now. I need to investigate how the automatic git version updating works in the pkgver() function, since what I have in the code now obviously doesn't work.

Anyway, for now, we're up to the latest version.

MithicSpirit commented on 2021-05-18 20:09 (UTC)

@cedricroijakkers looking at your previous (and pinned) comment I think you might have forgotten to push this change. The current PKGBUILD still pulls from the commit with tag 1.55.1, rather than latest commit.

FuzzyMidnight commented on 2021-04-10 20:55 (UTC)

thanks!

cedricroijakkers commented on 2021-04-10 15:26 (UTC)

This package is now the git build of the very latest commit on the VSCodium branch. If you wish to use the latest released version, switch to the vscodium package.

FuzzyMidnight commented on 2021-04-08 06:42 (UTC)

Can you move this package to vscodium? -git packages are usually used for packages which target the latest commit automatically. This is just a source build which would be well suited with package name vscodium

cedricroijakkers commented on 2021-03-16 06:58 (UTC)

Thanks for the recommendation CAofRH, I've updated the build.

CAofRH commented on 2021-03-14 01:18 (UTC)

The TRAVIS_OS_NAME env variable isn't really doing anything right now, only the unset OS_NAME is. In fact, a specific part of the build process is being skipped because of the OS_NAME variable not being set to anything. I suggest replacing TRAVIS_OS_NAME for OS_NAME in the PKGBUILD.

« First ‹ Previous 1 2 3 4 Next › Last »