3 ms·

That's fantastic! I've been trying to package as many apps as I can as flatpak (because flatpak rocks, fight me), I will definitely look into winepak to package

That's fantastic! I've been trying to package as many apps as I can as flatpak (because flatpak rocks, fight me), I will definitely look into winepak to package Windows-only software. The fact that it uses a standard and common-place technology, it just needs more exposure IMO. This is the first time I have heard of it. EDIT: nevermind... $ flatpak remote-add --if-not-exists winepak https://dl.winepak.org/repo/winepak.flatpakrepo error: Signature made Fri 20 Jul 2018 03:30:34 BST using RSA key ID A959831C080B608F BAD signature from " <julian@richen.io>" Key expired Tue 09 Jun 2020 19:16:34 BST

alvarlagerlof 5y ago
It's not active anymore.
- MayeulC 5y ago
  Which is a real shame. I can definitely see some value in winepak, and flatpaks could be built from Lutris install scripts, etc. I don't have much interest in windows apps, but I wouldn't mind donating a bit of money (as opposed to free time) to the project. Edit: https://github.com/winepak/winepak/issues/23#issuecomment-644956680 https://github.com/winepak/winepak/issues/23#issuecomment-64... > The biggest issue with winepak, which is why I haven't been working on it, is that it all revolves around me building things instead of a remote server doing it and having people contribute. I really just need to get the buildbot & sdk in a place that it can auto build an push out. Then it can do all the signing and building again and this shouldn't happen. I just need to find the time. Maybe a few PR around automation, and/or donated CI runtime could help a whole lot?