Open NullPlane opened 3 months ago
I don't want to personally support Winget, this adds more work for each release for me, unless it's automated as in with Flatpak, I do think this is something that community should take the effort if they are willing to collaborate and enjoy Winget. If it's automated the initial work should be done by a collaborator, that's what happened with the flathub package (even though I don't promote it because flatpak package isolation have many limitations for ecode).
I'd suggest add an issuing label needs-collaboration
Recently discovered that there is a project called Komac, that has workflows like run-komac to ease up the process and there are entire release-workflows for winget-pkgs like winget-releaser and winget-updater... They seem to differ in the way they react to Releases or something... Think collab might be a good choice but idk maybe these are somehow convenient... I never worked with them so I may not judge...
I see a larger problem for Windows-users in the fact that the
program is portable in its nature. The installer-debate is still
unsolved (where it might be nice to actually integrate those
features into ecode itself? Or a plugin? Idk but at least a file
extension manager I guess? Or the classical winstaller as a
separate program just for install?). I use ecode daily and thus I
manually registered it in the Windows registry and assigned
tons of extensions... And start menu entries etc; idk if winget
can do that from .zip
s...
I realized that I had closed #120 too early and that this was still open. Tho my Issue was not well formulated.
Its a less-priority feature. I hereby just open this Issue for the bucket list purpose in case someone else looks it up.