Package Details: vscodium-bin 1.97.2.25045-1

Git Clone URL: https://aur.archlinux.org/vscodium-bin.git (read-only, click to copy)
Package Base: vscodium-bin
Description: Binary releases of VS Code without MS branding/telemetry/licensing.
Upstream URL: https://github.com/VSCodium/vscodium
Licenses: MIT
Conflicts: vscodium
Provides: codium, vscode, vscodium
Submitter: ckatri
Maintainer: sperg512 (Icelk)
Last Packager: Icelk
Votes: 317
Popularity: 7.73
First Submitted: 2020-09-23 18:58 (UTC)
Last Updated: 2025-02-14 19:01 (UTC)

Pinned Comments

sperg512 commented on 2021-05-12 00:31 (UTC) (edited on 2024-06-04 15:14 (UTC) by sperg512)

@Icelk set up a script that checks for new releases and pushes updates if there are any new ones. I believe it runs every hour so there's no need to flag OOD, unless there's something that needs changed with the PKGBUILD.

Latest Comments

« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 Next › Last »

lkrms commented on 2020-12-19 10:52 (UTC)

@teras Respectfully, they're not separate projects. They're distinct builds of the same project, following identical release schedules and versioning. From the VSCodium home page: "The VSCodium project exists so that you don’t have to download+build from source. This project includes special build scripts that clone Microsoft’s vscode repo, run the build commands, and upload the resulting binaries for you to GitHub releases."

It's supposed to work as a drop-in replacement for VS Code. Removing this symlink disrupts that (IMHO).

teras commented on 2020-12-19 08:36 (UTC)

@ikrms IMHO the one project is called "code", the other "codium". If someone requires "codium" to point to "code", just do so. And as a general Unix user, I feel more comfortable to just create this symlink instead of having to use a platform specific and not everyday used "overwrite" or "nodeps" option instead.

lkrms commented on 2020-12-19 04:05 (UTC)

The removal of /usr/local/bin/code has broken several of my workflows, and the fact that it's only been done to facilitate installation of proprietary extensions that depend on the proprietary build of VS Code seems at odds with the open-source spirit of both VSCodium and Arch Linux, in my opinion. I would have thought users who require such extensions, and are willing to install multiple variants of VS Code to use them (including manually resolving the conflicts that arise from doing so) would receive little benefit from using VSCodium over VS Code and/or be comfortable using pacman's --overwrite and --nodeps options.

But that's just one user's opinion! Thanks for your consistent and responsive efforts maintaining this package :)

sperg512 commented on 2020-12-17 18:27 (UTC)

@cradcore removed, thanks

sperg512 commented on 2020-12-17 18:22 (UTC)

@pryme-svg no need to make a comment, as I already get notifications for new releases + flags out of date. Thanks though

pryme-svg commented on 2020-12-17 18:18 (UTC)

1.52.1 has been released upstream

https://github.com/VSCodium/vscodium/releases/download/1.52.1/VSCodium-linux-x64-1.52.1.tar.gz

cradcore commented on 2020-12-16 15:44 (UTC) (edited on 2020-12-16 15:46 (UTC) by cradcore)

@sperg512 I tried to edit it and accidentally deleted it. But thank you! The only other thing is line 39 of the PKGBUILD, that needs to be removed as well. That will fail if code is installed on the system

sperg512 commented on 2020-12-14 19:01 (UTC)

@cradcore already did, why'd you delete the last comment?

cradcore commented on 2020-12-14 19:00 (UTC) (edited on 2020-12-16 15:44 (UTC) by cradcore)

@sperg512 please remove the code and vscode conflicts. There are several proprietary extensions that only work with Microsoft's build of VSCode, and it is a big pain to have to uninstall VSCodium every time we need to use one of these extensions

sperg512 commented on 2020-12-14 18:58 (UTC)

ok

« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 Next › Last »