Arch Linux User Repository

I rarely use vscoduim. As such I might miss the update. I adopted this package, because it was left orphen for a long time. This package is equal to vscodium-bin-features 1.82.0-4. If version changes, I will update it if someone puts a comment here or email me.

I rarely use vscoduim. As such I might miss the update. I adopted this package, because it was left orphen for a long time. This package is equal to vscodium-bin-features 1.82.0-4. If version changes, I will update it if someone puts a comment here or email me.

We can always have the PKGBUILD patch the patch.py file 😉 😅

package() {
 install -Dm 644 "${srcdir}/${pkgname}.hook" "${pkgdir}/usr/share/libalpm/hooks/${pkgname}.hook"
 sed -i -E 's:(PRODUCT_JSON_LOCATION *= *).*:\1"/usr/share/vscodium/resources/app/product.json":' "${srcdir}/patch.py"
 install -Dm 755 "${srcdir}/patch.py" "${pkgdir}/usr/share/${pkgname}/patch.py"
}

@ika Nope, not in /usr/share, but in /opt, but then vscodium, not vscodium-bin (you probably intended that).

The funny thing in my case is that this is why this patch successfully changed my product.json for the vscodium-bin package for me (I feel no need to build it from source myself), before realizing that I should actually use vscodium-bin-features instead. :)

But this one should patch the one for vscodium indeed, not the for vscodium-bin version.

The patch.py script for both is now exactly the same in both patches here on AUR.

If I was the author of these 2 patches, I would just change this python script in such way that it searches for both paths and changes the one found, making it easier to copy-paste file between both without this mistake.

This is valid because vscodium and vscodium-bin cannot be installed at the same time (exclusion in PKGBUILD made by conflicts setting).

It still has the wrong path, should be /usr/share/vscodium/resources/app/product.json not /opt/vscodium-bin/resources/app/product.json

patch.py contains the wrong path of the product.json

Ahoj,

when I do a fresh installation of vscodium, and then vscodium-features, and then launch vscodium after having removed it's user config, it fails to start with

vscodium 
node:internal/modules/cjs/loader:1190
    throw err;
    ^

SyntaxError: /usr/share/vscodium/resources/app/product.json: Unexpected token e in JSON at position 2976
    at parse (<anonymous>)
    at Module._extensions..json (node:internal/modules/cjs/loader:1187:22)
    at Module.load (node:internal/modules/cjs/loader:988:32)
    at Module._load (node:internal/modules/cjs/loader:829:12)
    at c._load (node:electron/js2c/asar_bundle:5:13343)
    at Module.require (node:internal/modules/cjs/loader:1012:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/usr/share/vscodium/resources/app/out/cli.js:4:9247)
    at Module._compile (node:internal/modules/cjs/loader:1118:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1173:10)
    at Module.load (node:internal/modules/cjs/loader:988:32)
    at Module._load (node:internal/modules/cjs/loader:829:12)
    at c._load (node:electron/js2c/asar_bundle:5:13343)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47

When I do not install vscodium-features (I need to reinstall vscodium, though, since the reversal of the patches of vscodium-features seems not to work fully), then vscodium starts.

Regards!

What are the feature that we r talking about?