Search Criteria
Package Details: vscodium-electron 1.95.3.24321-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/vscodium-electron.git (read-only, click to copy) |
---|---|
Package Base: | vscodium-electron |
Description: | VS Code without MS branding/telemetry/licensing. - System-wide Electron edition |
Upstream URL: | https://github.com/VSCodium/vscodium |
Keywords: | code codium electron system vscode vscodium wayland |
Licenses: | MIT |
Conflicts: | codium, vscodium, vscodium-bin, vscodium-git |
Provides: | codium, vscodium |
Submitter: | m00nw4tch3r |
Maintainer: | Richardn |
Last Packager: | Richardn |
Votes: | 8 |
Popularity: | 0.75 |
First Submitted: | 2022-04-10 18:19 (UTC) |
Last Updated: | 2024-11-19 02:42 (UTC) |
Dependencies (11)
- electron32 (electron32-binAUR)
- libsecret
- libx11 (libx11-gitAUR)
- libxkbfile
- ripgrep (ripgrep-gitAUR)
- git (git-gitAUR, git-glAUR) (make)
- jq (jq-gitAUR) (make)
- nvmAUR (nvm-gitAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- gvfs (gvfs-gitAUR) (optional) – For move to trash functionality
- libdbusmenu-glib (optional) – For KDE global menu
Required by (4)
- vscodium-electron-features
- vscodium-electron-marketplace
- vscodium-features (requires vscodium)
- vscodium-marketplace (requires vscodium)
Latest Comments
1 2 3 4 5 6 Next › Last »
Richardn commented on 2024-10-08 17:00 (UTC) (edited on 2024-10-10 13:55 (UTC) by Richardn)
For those of you waiting for an update: For the latest 1.94 updates, I indeed managed to tweak stuff a bit according to the updated build process, so that this package builds. But after install, calling
codium
will just spawn a vscodium process with nothing showing up on the screen.gdb
sayselectron
is blocking on appoll()
. I am completely loss what is happening. I am asking others for help, and also I may wait for the official code package to update (they also use system electron) and see how they do stuff.--- 2024/10/10 Update ---
Update is online. This helped in updating
vscodium.js
, otherwise as described above, software will simply not start.By the way, although
electron30
is the officially supported version, by my own experienceelectron32
also works fine (andvscode
upstream is already testing withelectron32
). If you want to have a try, just change_electron
toelectron32
and_nodejs
to"20.17.0"
inPKGBUILD
.Richardn commented on 2024-09-10 02:45 (UTC)
Quite a coincidence that just after I pushed the new update, with update to
electron30
, I see your @coxackie's comment xd. Also, thePKGBUILD
is designed in a way so that anyone can change the electron version used (without any guarantees of course). Handy for anyone who only want ONE electron in their system.coxackie commented on 2024-09-09 16:42 (UTC)
I thought
electron30
was used already in 1.92...backbord commented on 2024-07-09 14:55 (UTC) (edited on 2024-07-09 14:55 (UTC) by backbord)
@Richardn Thank you very much! Works like a charm!
Another thing I noticed: When I try to open a file in vscodium it will open a new, but empty, instance of vscodium. Found out that removing the
--unity-launch
in the desktop file fixed it, as it is deprecated. It was also removed in the upstream: https://github.com/VSCodium/vscodium/pull/1866Richardn commented on 2024-07-03 06:38 (UTC)
@backbord Fix in place. I also put my understanding of the fix as comments in
vscodium.js
.By the way, seems like electron release 29.4.3 is officially online now, so we do not need the dirty fix mentioned above with
electron29
.backbord commented on 2024-07-02 08:52 (UTC)
Can we get the proposal https://aur.archlinux.org/packages/vscodium-electron#comment-969003 merged? This is the last thing that is required to fix wayland.
Richardn commented on 2024-06-20 02:37 (UTC)
Another day without
electron29
update, so you will still be needing the dirty fix mentioned above if you want to build withelectron29
.By the way, as a followup to this convo, as now I completely understand the packaging process, I can answer:
ripgrep
is being depended on because in the usualvscodium
package,electron
andripgrep
are the only two binary executables present in the compiled files. It is then reasonable for this package to remove both of them and link the system versions of them instead.Richardn commented on 2024-06-11 11:42 (UTC) (edited on 2024-06-11 15:22 (UTC) by Richardn)
I am working on the major v1.90 update, which upgrades to
electron
29 and node20.9.0
. However a confusing situation is found: The latest electron 29 version is 29.4.2, however theelectron29
in the Arch repo is 29.4.3. This breaks build as the process can't find the source on GitHub for the system electron installed. I have alerted several Arch community managers about this and we are investigating.--- Update ---
Issue for the electron problem is here
I already updated this repo anyways. By design, you can choose whatever version of system electron to use by modifying the PKGBUILD (of course no one can guarantee that things will run fine).
But, if you choose
electron29
, due to the issue mentioned above, build will fail. A nasty solution is, modify/usr/lib/electron29/version
to be29.4.2
. This can trick the build system into getting electron v29.4.2 source files instead. I did this and the editor appears fine with me so far.Richardn commented on 2024-05-07 14:21 (UTC)
A note from maintainer me: I am still alive and will check and update this package soon. Just that these two weeks I am graduating, moving out from my apartment, preparing US departure, etc., TLDR too busy to do anything else. Sorry for the delay, I will definitely come back to this soon.
flavionm commented on 2024-05-03 21:25 (UTC)
Is there any reason why the compiled VSCodium has a different release number than the package indicates? Mine has version 24124, while this package is currently 24102.
1 2 3 4 5 6 Next › Last »