[ENHANCEMENT] Windows support? #11

rhyses-pieces commented 2025年03月06日 06:44:48 +01:00

Windows support

I think this config is a great idea! Is there any possibility of supporting Windows? I tried setting this up with BetterBird, and it seemed to work - except Chat is still enabled? So I'm not sure if I correctly installed it. This would make this more accessible to a potentially large pool of users, since I'd imagine there's not a few people using Thunderbird on Windows platforms.

Windows compatibility could be accomplished through a PowerShell script? A good example of this is Spicetify, which installs a config for Spotify. Not sure if that example applies here, but happy to hear thoughts on this.

### Windows support I think this config is a great idea! Is there any possibility of supporting Windows? I tried setting this up with BetterBird, and it seemed to work - except Chat is still enabled? So I'm not sure if I correctly installed it. This would make this more accessible to a potentially large pool of users, since I'd imagine there's not a few people using Thunderbird on Windows platforms. Windows compatibility could be accomplished through a PowerShell script? A good example of this is Spicetify, which [installs a config](https://spicetify.app/docs/getting-started/) for Spotify. Not sure if that example applies here, but happy to hear thoughts on this.

celenity commented 2025年03月06日 07:04:20 +01:00

I would indeed like to support Windows (for both Dove & Phoenix) - but it's admittedly proven difficult to do so. The biggest problem comes down to the fact that I just don't use Windows, and unfortunately no one's been able to contribute/provide assistance. What I'd like to do ideally is create a package (similar to how we do for GNU/Linux distros & macOS) that users can simply install and update with the rest of their system.

I've looked into Chocolatey - but my understanding is that packaging for Chocolatey requires Windows, so that's out (I don't mind testing things on a Windows VM; but I need an easy and reliable way to package and deliver updates...). I've heard that winget is possibly an option as well, but I haven't yet properly looked into it. Of course any other ideas here are appreciated...

Windows compatibility could be accomplished through a PowerShell script? A good example of this is Spicetify, which installs a config for Spotify. Not sure if that example applies here, but happy to hear thoughts on this.

I'll have to take a look at their script; I think my biggest concern with an approach like this would be a lack of seamless/automatic updates. That being said, having some kind of script would probably be better than nothing in the short-term, so might be worth looking into.

I would indeed like to support Windows (for both Dove & Phoenix) - but it's admittedly proven difficult to do so. The biggest problem comes down to the fact that I just don't use Windows, and unfortunately no one's been able to contribute/provide assistance. What I'd like to do ideally is create a package (similar to how we do for GNU/Linux distros & macOS) that users can simply install and update with the rest of their system. I've looked into Chocolatey - but my understanding is that packaging for Chocolatey requires Windows, so that's out *(I don't mind testing things on a Windows VM; but I need an easy and reliable way to package and deliver updates...)*. I've heard that winget is possibly an option as well, but I haven't yet properly looked into it. Of course any other ideas here are appreciated... > Windows compatibility could be accomplished through a PowerShell script? A good example of this is Spicetify, which installs a config for Spotify. Not sure if that example applies here, but happy to hear thoughts on this. I'll have to take a look at their script; I think my biggest concern with an approach like this would be a lack of seamless/automatic updates. That being said, having some kind of script would probably be better than *nothing* in the short-term, so might be worth looking into.

rhyses-pieces commented 2025年03月06日 08:02:12 +01:00

From what I could glean from both Chocolatey and winget, they both utilize PowerShell scripts for the actual installation. Authoring manifests for winget seems to require the same dependencies as Chocolatey? Moreover, it seems like winget requires an executable installer. Although it seems like .zip files seem to have some compatibility but require more setup (source here). I did find a tool that still helps you author manifests for winget on platforms outside of Windows here.

I also wanted to offer another tool for installing apps: scoop. Authoring manifests for scoop seems cross-platform compatible and a little less headache-inducing from what I could tell from the docs.

I'll have to take a look at their script; I think my biggest concern with an approach like this would be a lack of seamless/automatic updates. That being said, having some kind of script would probably be better than nothing in the short-term, so might be worth looking into.

For winget, you'd need a GitHub token to automatically generate a new manifest for building GitHub actions I think? I could be wrong. Here's the docs for more info. But for Chocolatey, there's some support it seems? For scoop, you could link some scripts for upgrading in the pre_install field in the manifest file?

I've barely touched PowerShell scripting, so I'm not sure if I can help out a lot. I can help test and validate packages maybe?

From what I could glean from both Chocolatey and winget, they both utilize PowerShell scripts for the actual installation. Authoring manifests for winget seems to require the same dependencies as Chocolatey? Moreover, it seems like winget _requires_ an executable installer. Although it seems like `.zip` files seem to have some compatibility but require more setup ([source here](https://github.com/microsoft/winget-pkgs/blob/master/doc/manifest/schema/1.9.0/installer.md#:~:text=InstallerType%20%2D%20Enumeration%20of%20supported%20installer%20types.,-Required%20Field)). I did find a tool that still helps you author manifests for winget on platforms outside of Windows [here](https://github.com/russellbanks/Komac). I also wanted to offer another tool for installing apps: [scoop](https://scoop.sh/). Authoring manifests for scoop seems cross-platform compatible and a little less headache-inducing from what I could tell from the docs. > I'll have to take a look at their script; I think my biggest concern with an approach like this would be a lack of seamless/automatic updates. That being said, having some kind of script would probably be better than nothing in the short-term, so might be worth looking into. For winget, you'd need a GitHub token to automatically generate a new manifest for building GitHub actions I think? I could be wrong. [Here's the docs](https://github.com/russellbanks/Komac?tab=readme-ov-file#github-token) for more info. But for Chocolatey, there's [some support](https://docs.chocolatey.org/en-us/create/create-packages/#upgrading) it seems? For scoop, you could link some scripts for upgrading in the [`pre_install` field](https://github.com/ScoopInstaller/Scoop/wiki/App-Manifests#:~:text=pre_install%3A%20Same%20options%20as%20post_install%2C%20but%20executed%20before%20an%20application%20is%20installed.) in the manifest file? I've barely touched PowerShell scripting, so I'm not sure if I can help out a lot. I can help test and validate packages maybe?