Updating this package to 0.13.x is currently held up because we do not have electron23 packages available yet. In the mean time as usual the chrysalis-bin package is the upstream recommended way and currently up to date. This package is is for the purists and hackers ;-)
Search Criteria
Package Details: chrysalis 0.13.3-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/chrysalis.git (read-only, click to copy) |
|---|---|
| Package Base: | chrysalis |
| Description: | Graphical configurator for Kaleidoscope-powered keyboards |
| Upstream URL: | https://github.com/keyboardio/Chrysalis |
| Licenses: | GPL3 |
| Submitter: | alerque |
| Maintainer: | alerque |
| Last Packager: | alerque |
| Votes: | 5 |
| Popularity: | 0.052210 |
| First Submitted: | 2020-10-05 21:13 (UTC) |
| Last Updated: | 2024-03-27 23:31 (UTC) |
Dependencies (12)
- electron23 (electron23-binAUR)
- fuse2
- uucp
- git (git-gitAUR) (make)
- jq (jq-gitAUR) (make)
- moreutils (make)
- node-gyp (corepackerAUR) (make)
- nodejs-lts-hydrogen (make)
- npm (corepackerAUR) (make)
- squashfs-tools (squashfs-tools-gitAUR) (make)
- yarn (corepackerAUR, yarn-pnpm-corepackAUR, yarn-berryAUR) (make)
- zip (zip-natspecAUR) (make)
Required by (0)
Sources (2)
alerque commented on 2023-05-11 06:24 (UTC)
alerque commented on 2022-10-26 21:35 (UTC) (edited on 2022-10-26 21:36 (UTC) by alerque)
Just to follow up, since updating this package to 0.12.0 I've used it to flash my Atreus from 0.90.0 to 0.91.0 and tweak some layouts to confirm that everything is working. Just for grins I did this on a fresh computer I just built from scratch yesterday with no previous Chrysalis install of any kind just to confirm everything works without any possible leftovers from old versions. I'm happy to help trouble shoot any reported problems using the system Electron like this, but so far I don't know what I'm supposed to look for.
alerque commented on 2022-10-22 17:32 (UTC) (edited on 2022-10-22 18:02 (UTC) by alerque)
@algernon
It doesn't work. It will not work in its current form.
I don't doubt you have experiences to this effect, but can we be a little more specific? My experience is it does work. I suspect what you hint at (finding resources) is a bug that should be fixable upstream, but if I had something to actually test it would help a lot.
I've been using this build exclusively for a couple years since I got my first related hardware. The big warning (warning not error) doesn't really clarify what exactly is expected not to work. I've used it to update my Atreus keyboard (firmware and layout) many times including recently. My Model 100 is still with China Post somewhere so I haven't had the pleasure of testing on that yet.
algernon commented on 2022-10-18 08:43 (UTC) (edited on 2022-10-18 08:44 (UTC) by algernon)
@eclairevoyant That's reasonable. In that case, using the bundled electron would fix the package. If that's not an option, then there's no solution but deleting it, it's not gonna work with an external one.
eclairevoyant commented on 2022-10-17 16:37 (UTC)
@algernon packages that don't end in -bin must build from source, using the appimage for this package is a nonstarter.
@alerque can you explain further about why this package must use the system electron executable? is there a bug when using the bundled electron, and if so, was that reported to upstream?
algernon commented on 2022-10-17 16:02 (UTC) (edited on 2022-10-17 16:03 (UTC) by algernon)
@alerque: How about not having a broken package on AUR instead? Like, remove it. Or simply copy chrysalis-bin over. Anything.
"This arrangement works for some tasks"... I mean... Chrysalis displays a big error* on start. What task is it even good for in its current form?
*: https://s3.madhouse-project.org/paste/chrysalis/screenshots/chrysalis-aur-0.11.8-2.png
It doesn't work. It will not work in its current form.
Do I have to make it fail to compile on Arch, or will you do the right thing and either delete the package, or fix it by using the official AppImage a'la chrysalis-bin, or a bundled electron a'la chrysalis-git?
alerque commented on 2022-10-12 11:30 (UTC) (edited on 2022-10-22 17:45 (UTC) by alerque)
PLEASE CONSIDER USING chrysalis-bin, using the system Electron executable as this package does is (according to upstream developers) known to cause issues, bundling the project one here goes against Arch packaging guidelines and runs into other issues. This arrangement works for some tasks (me and my Atreus keyboard are happy) but not others (e.g. see reports below of not being able to flash Model 01s). If you just want your keyboard to work and be supported by upstream the -bin package is the way to go. If you a source purist and want to debug issues yourself, go for it.
algernon commented on 2022-10-09 00:17 (UTC)
@eclairevoyant No, it wouldn't, because running with an external Electron would still break half the functionality, it still wouldn't be able to find its static assets.
The only way Chrysalis should be run is with the dependencies it lists, as it is built upstream. Anything else will break it in subtle ways. Been there, tried it, didn't work.
Build from source, unmodified, with bundled Electron: sure thing! That's pretty much what chrysalis-git does, last I checked. Use the AppImage we provide upstream, as is: sure thing! Anything else is just aiming a gun at your own feet. You may miss, but it's better if you just put the gun down.
eclairevoyant commented on 2022-10-08 18:17 (UTC)
@algernon wouldn't just changing the dependency to electron17 fix this issue?
algernon commented on 2022-10-06 12:02 (UTC)
FWIW, running Chrysalis with an Electron other than the one we bundle with the AppImage is not supported. It will break. Running it with an external electron is similarly unsupported. Electron 18 and 19 introduce regressions in Chrysalis, thus, we are unable to update our dependency until we find a solution for those.
We (Chrysalis upstream) are unable to help with issues arising from using the chrysalis package from AUR. If for some reason you can't use the official AppImage, the chrysalis-bin package is a reasonable compromise.
Pinned Comments
alerque commented on 2022-10-12 11:30 (UTC) (edited on 2022-10-22 17:45 (UTC) by alerque)
PLEASE CONSIDER USING
chrysalis-bin, using the system Electron executable as this package does is (according to upstream developers) known to cause issues, bundling the project one here goes against Arch packaging guidelines and runs into other issues. This arrangement works for some tasks (me and my Atreus keyboard are happy) but not others (e.g. see reports below of not being able to flash Model 01s). If you just want your keyboard to work and be supported by upstream the -bin package is the way to go. If you a source purist and want to debug issues yourself, go for it.