Arch Linux User Repository

@evybongers Sure I'd accept a patch to that effect. The icon should be downloaded using the source=() array if anything. Generating the desktop with gendesk is fine, or just add it as a source tracked along with the PKGBUILD. The sources are in this repo so sending a PR is fine.

Could you maybe add a desktop entry for it? Something like this:

[Desktop Entry]
Terminal=false
Type=Application
Name=Chrysalis
Comment=Graphical configurator for Kaleidoscope
Exec=/usr/bin/chrysalis
Icon=chrysalis
StartupWMClass=chrysalis

Icon could be downloaded from https://github.com/keyboardio/Chrysalis/blob/v${pkgver}/build/icon.png and installed as /usr/share/applications/io.keyboard.chrysalis.desktop

I'm happy to send a patch for it

Yes we can probably make this place the udev rules, but we also have to figure out how to strip out the root prompt and script that tries to place it. If anybody has patches they are welcome, I'm traveling and unable to test updates at the moment.

Would it be possible for this package (as well as chrysalis/chrisalis-git I presume) to install the upstream udev rules to /etc/udev/rules.d at install time?

While upstream prompts for root rights with a script to install it, it seems nicer to have it installed and tracked by pacman - also, it turns out upstream doesn't actually install it in all situations it'd be needed (if you're in the uucp group, you can access the serial port, but not do firmware updates without manually installing the udev rules).

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.

@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.

@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?

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.

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.

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.