Package Details: chrysalis-bin 0.7.9-1

Git Clone URL: https://aur.archlinux.org/chrysalis-bin.git (read-only, click to copy)
Package Base: chrysalis-bin
Description: Graphical configurator for Kaleidoscope-powered keyboards (AppImage)
Upstream URL: https://github.com/keyboardio/Chrysalis
Licenses: GPL3
Conflicts: chrysalis
Provides: chrysalis
Submitter: caleb
Maintainer: caleb (fx101, pdizzle)
Last Packager: caleb
Votes: 0
Popularity: 0.000000
First Submitted: 2020-10-05 13:49
Last Updated: 2020-10-05 13:51

Latest Comments

1 2 Next › Last »

caleb commented on 2020-10-07 10:51

Is someone able to confirm that this AppImage works properly without the uucp package installed? In working on the source build I was unable to get that working without it — presumably not for the tooling it provided but just to get the /dev/ttyACM0 device permissions and uucp user group setup properly. It might be needed as a dependency for this package as well, but it's kind of hard to backtrack on my system and test without it.

caleb commented on 2020-10-05 19:57

@pdizzle The current chrysalis-git is closer to correct already, it at least builds the source, although it handles the Electron dependency incorrectly and has other issues such as mixing up npm and yarn. I may look into that after I fix up the chrysalis package. Yes of course chrysalis will track tagged stable release versions. The git package builds from the latest HEAD rather than the latest tagged release.

pdizzle commented on 2020-10-05 14:16

@caleb, thanks for doing that. just so I'm following, what would be the difference between chrysalis and chrysalis-git at that point? would you be tracking releases on chrysalis?

caleb commented on 2020-10-05 13:56

This package is (and always has been) incorrectly named. It is just packaging an AppImage that is built upstream, so the pkgname should be chrysalis-bin. I have done the work for you guys of posting it under that name including importing this repository history and updating the packaging to work under that name. I've also added the existing maintainers as maintainers (I'll remove myself later). I'm now filing a merge request to get rid of this package namespace so that I can post an actual source build under this name.

pdizzle commented on 2020-07-22 14:03

OK -- based on looking through AppImage docs and some discussion, it looks like libfuse.so.2 is needed in order to be able to run AppImages, so i will be adding fuse2 as a dependency.

pdizzle commented on 2020-07-22 01:11

I've updated the package to 0.7.9 -- I have not added fuse2 as a dependency yet.. waiting until I hear back from the devs -- my best guess is this is included in Ubuntu and that's what the AppImage is packaged for, so the dep is not included in the AppImage. If that's the case, I'll update the deps to include that as well. Thanks for the catch @hxy.

pdizzle commented on 2020-07-21 23:12

@hxy -- apparently i have that installed and so i hadn't noticed this. I'm hesitant to add that as a dependency as this is an appimage and should be "bundled" with all dependencies (hence there currently being none, including node and electron that this runs on). I would recommend opening an issue with the main repository. Thanks for reporting here, it's definitely good to note for the time being. Also will be updating to 0.7.9 shortly, perhaps that will be fixed.

hxy commented on 2020-07-21 20:19

I had to install the fuse2 package as the AppImage wouldn’t run without libfuse. Should this be added to the PKGBUILD as a dependency?

fx101 commented on 2020-04-18 05:13

Apologies for the delay! I'll do a better job updating it in the future.

pdizzle commented on 2020-04-17 03:37

to install latest version:

bump pkgver to 0.7.4 sha512sum to 1dd9dba6e89719db7be5087326c5493a76d4bde826d6507af6c92e495682b3108d2bb45e954d6e7dc26650d740b4b11daedcfec8f68caf6321d0cb6c1dfdd7ab