brew on macos and choco on windows support

[mhmdio]

Feature request:

https://brew.sh/ to install the app on mac.
https://chocolatey.org/ to install the app on windows.

[andreacavagna01]

Great idea!
Have you ever posted some app on Brew or Chocolatey?

[andreacavagna01]

absolutely! let's join our discord chat and meet the team :)

https://discord.gg/Pt5V2Sz6

[mhmdio]

The link has expired, can you send it again?
Thanks.

[andreacavagna01]

https://discord.gg/r8vG4c6

I'm sorry 👍

[sheldonhull]

Big fan of chocolatey, but wanted to mention that Scoop might be easier initially as it's in a centralized repo.
I know Go based tooling has automatic Scoop package generation, so maybe using Scoop will get this up and running much more easily. I've got a lot of choco experience but it requires auto package updating and has some nuances to handling that those not familiar with it specifically might find a bit more confusing than the more "bash/shell" oriented approach of Scoop.

https://github.com/lukesampson/scoop/wiki/App-Manifests

[andreacavagna01]

I Will look at Scoop, never used it, usually, I use brew, to me, have this packager support comes with the version with Leapp client and Daemon.
@ericvilla and @pethron I think Scoop is something you should watch

[ericvilla]

We’ve to understand how to fit it in both Desktop App and Daemon installation process. It would be a nice thing if we’re able to create a single installation workflow with Scoop. I’ll take some time to test it on both the Desktop App and the Daemon!

…

On 22 Apr 2021, at 11:08, Andrea Cavagna ***@***.***> wrote: I Will look at Scoop, never used it, usually, I use brew, to me, have this packager support comes with the version with Leapp client and Daemon <https://github.com/Noovolari/leapp-daemon>. @ericvilla <https://github.com/ericvilla> and @pethron <https://github.com/pethron> I think Scoop is something you should watch — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#51 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADZC4BHKURR36IEHP6UBMNDTJ7RRDANCNFSM4VAEHEBA>.

[ericvilla]

@sheldonhull, based on your availability, we could keep in touch, so you can introduce me to the tool! Then we can study together how it can fit with Leapp

[sheldonhull]

Would love too. On macOS but if I can help I'll do my best for sure!

[andreacavagna01]

Can anyone help me with Chocolatey? It's been pointed out again by @robcube, @mhmdio. How should I help to complete this task?

[sheldonhull]

Did you look at scoop instead? Go releaser makes this automatic I think

[sheldonhull]

I'd be willing to do my best to help out.
I forked both repos, but realize there is something a bit challenging in this.

Normally a single repo would contain the project so I could configure goreleaser to build.
This is multi-repo but designed to be distributed as a single package.
Not sure how to properly handle that.

I have a lot of ci config files for running golanglint-ci, markdown formatting autofix, security scans, builds and more. Nothing yet for multi-repo builds.

Btw, last quick tip. Try replacing your Makefile with go-task. It's cross-platform and works on windows. Pretty easy to copy and paste your make file into. (install direction snippet here I'm personally trying to use goyek which is a go based task tool, but it's more complex.

[ericvilla]

I didn't investigate golang release process yet, but my initial idea was to configure a service around the goland-based daemon. I've already tried kardianos package but it seems to be a little bit immature when it has to deal with the macOS service ecosystem. Do you know that library?

What about installing and starting the golang-based daemon service during the electron-based client installation?
IMO, it is a good way to handle the lifecycle of the daemon even if the client app fails. Moreover, it could be a game-changer when developing the CLI.

Currently, the makefile is used only to generate go-swagger documentation, so we can move go-task if it covers what is already defined in the makefile. I personally have to study both go-task and go-releaser to understand how they fit with the creation of a single bundle.

[andreacavagna01]

Looks like it has been added from this issue:
#179