clearly i must hate myself because i'm trying to package vscodium for Void

which also involved writing an nvm package for Void

@kim why are you doing this to yourself

@sys64738 i want vscodium as a Void package, so i can later write an encompassing package that builds an appimage from that result :')

@sys64738 which probably sounds more unhinged than even just packaging vscodium... but i know what i want!

@kim never have i been more happy to be a neovim user

@sys64738 watch-out or i'll appimage neovim too!

there we go, vscodium and nvm:

https://codeberg.org/gruf/void-packages/src/branch/main/srcpkgs/vscodium/template
https://codeberg.org/gruf/void-packages/src/branch/main/srcpkgs/nvm/template

not quite perfect, as ideally i'd like it building the required electron version from source, or using the system electron version, but that's a later problem :P

also the nvm do_check stage fails on like 23 tests, but succeeds on 129, and generally works, so 🤷‍♀️

dammit our repo electron version is way out of sync... time to look at updating that 😭

looking to arch to crib from theirs: https://gitlab.archlinux.org/archlinux/packaging/packages/electron39/-/blob/main/PKGBUILD?ref_type=heads

good fucking lord

okay seems might be simpler if i just use electron's own build tool for this, as their github release workflow does: https://github.com/electron/electron/blob/main/.github/actions/build-electron/action.yml

the question is will electron take more or less time to build than the Linux kernel!

oh no, google version management tools 😭 https://chromium.googlesource.com/chromium/tools/depot_tools.git/+/HEAD/README.gclient.md

maybe I'll just add an electron-bin package for now that pulls the latest release binaries lol.

@kim more ime