Package Details: vscodium-git 1.89.1.24130.r0.g02a9d03-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: 6
Popularity: 0.000176
First Submitted: 2020-03-24 09:33 (UTC)
Last Updated: 2024-05-10 16:31 (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 2022-05-12 06:33 (UTC)

@Ashark: This package tracks the latest commit in the master branch of the vscodium.git repo in GitHub. VSCodium itself determines which commit in the vscode.git (Microsoft) repository they track. So if there is a commit in the vscode.git repo you would like to build, that is solely up to VSCodium. We are just tracking the changes in the vscodium.git repo here. What you would want, is a build of code-git, which is not VSCodium, but VSCode directly. I don't know if that package exists, though.

Ashark commented on 2022-05-11 21:32 (UTC)

Can anybody explain how this package works? I gust rebuilt it, hoping it will include a recent commit to not escape redirection symbol (https://github.com/microsoft/vscode/commit/c57173721932f37d4061b978cd8cece83a6b92a4). But I get a build of vscodium-git, in which's about window I see commit another commit number. The function I look for is not working.

I guess it may drop a very top commits. Is that true?

willemw commented on 2021-10-26 12:47 (UTC)

provides=('vscodium') is missing. 'vscodium-bin' in 'conflicts' is not necessary.

cedricroijakkers commented on 2021-09-07 11:34 (UTC)

@TedHartDavis: I hate M$ just as much as the next guy, but in this case it is actually on the team behind VSCodium. They take the VSCode code, and apply various patches to it, and it is one of these patches that is failing here.

Either way, since 1.60.0 has been released last night, they have fixed the issue, so the build is working again now. Probably they were in the process of merging the upstream code and making it work. I've noticed this happens usually a few days before the final release.

TedHartDavis commented on 2021-09-07 11:27 (UTC)

@cedricroijakkers that just makes me all the more disappointed with M$ (:

It's good to know that it's on them.

Thanks! (:

cedricroijakkers commented on 2021-09-06 06:53 (UTC)

@TedHartDavis that's indeed a problem upstream, it happens quite often that their main branch does not even build. With a bit of luck they should fix it in a couple of days, sadly there is nothing I can do about that...

TedHartDavis commented on 2021-09-05 00:45 (UTC)

Heyo! I presently lack the mental capacity to try to interpret this, but attempting to upgrade in paru, I can't.

Is this more of an upstream issue -- and one that will be fixed before anyone sees this comment? Maybe. Anyway, here's a shortened-for-brevity sequence leading to failure.

==> Starting build()...
[...]
applying patch: ../patches/fix-cors.patch
error: patch failed: src/main.js:174
error: src/main.js: patch does not apply
==> ERROR: A failure occurred in build().
    Aborting...

MithicSpirit commented on 2021-07-16 02:57 (UTC)

There should be a warning telling people to install jq prior to running makepkg because, even though it is in makedepends, since the PKGBUILD is sourced before installing dependencies (for obvious reasons), and jq is run when sourced (for the $source array), it will fail if jq is not installed. Ideally it would be possible to somehow wait to run jq until prepare() but ¯\_(ツ)_/¯

slimb commented on 2021-06-20 17:45 (UTC)

Since this package is a bit weird, and since someone may just be interested to see the latest vscodium update, but someone else may want to rebuild as soon as the latest vscode update hits, I think the only way to solve this issue for everyone would be to split this into 2 PKGBUILDs. One which tracks the latest vscodium commit, and one which tracks the latest vscode commit. And then you could put back in the pkgver function and not have to manually update this every other day.

MithicSpirit commented on 2021-05-20 12:13 (UTC)

I mean considering this is a -git package, breaking changes are the expectation, though it might be better to just go off of the latest vscodium commit and latest compatible vscode commit, in whichc case the pkgver should just be based on the vscodium commit imo.

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