[Feature Request] Add support for deploying WinSetView through Chocolatey

[fabiorzfreitas]

Basically, Chocolatey is apt-get for Windows. There are over 10 000 packages for installerd and portable software (and Chocolatey makes sure they don't bloat you environmental variables, and also keeps portable software organized!). It has support for auto-maintained/auto-updated packages and it's extensively documented, and supposed to be very streamlined for handling (pointing to the proper files, updating hashes, versioning etc.) releases from GitHub.

While anyone can submit and maintain packages for whatever software they'd like, sadly I won't be ready to deal with packages for quite some time, otherwise I would do it myself and then offer you ownership of the working self-maitained package, as it's always better if a package is maintained by the devs themselves.

Still, since WinSetView is in active development, perhaps this could be a little enhancement for a future release!

Thanks!

[LesFerch]

You make a strong case. I'll look into it and see what's involved.

[fabiorzfreitas]

You make a strong case. I'll look into it and see what's involved.

That's always a good thing to read :)

I think you'll find everything you'll need here:

• The Chocolatey Automatic Package Updater Module repo;
• The documentation pages that readme.md should be pointing to, on Chocolatey and the original wiki;
• And the linked video-tutorial.

Please note that even if readme.md has a broken link and a warning/disclaimer on top, this fork (from the user created original, and endorsed by Chocolatey) has been made in 2022, since its owner would/could not maintain it anymore.

As of March 2024, the Chocolatey Team released the new 1.0.0 version and announced the process of deprecating the original (and still functional) tool.

Thank you again!

[LesFerch]

Today I perused some of the documentation and it all looks more involved than I'd hoped, but isn't that always the case with something one has never done before? I haven't given up, but now I'm more intrigued by what you said earlier:

"While anyone can submit and maintain packages for whatever software they'd like, sadly I won't be ready to deal with packages for quite some time, otherwise I would do it myself and then offer you ownership of the working self-maintained package"

That would be ideal for me. Does "I won't be ready to deal with packages for quite some time" mean you're too busy or is there a technical issue? I totally understand being too busy. I just want to understand.

[fabiorzfreitas]

Well, busy, but not strictly: I'm currently dealing with a quite big data loss. I just finished undeleting files and extracting what I could from JSONs and HTMLs, but now I have a few dozen versions of a SQLite file that I need to tackle. Except that I need to learn SQLite from scratch (seems doable, though).

After that, I have plans for doing this Chocolatey thing for a handful of software, some of them abandoned, and I would do it all at once. Still, I'm fairly familiarized with Chocolatey, so perhaps it'll come easier to me. I guess I'll consider it as a side-project, something to do when taking a break from the SQLites!

It's possible I get this done in one go, but I also may give up (for now) if it gets too heavy on PowerShell, so I'll try to set this as a goal for one week or so, then I'll check back here!

[LesFerch]

Sounds good. Thanks!

[fabiorzfreitas]

Status update: got quite busy here, didn't work on it at all. But apparently it seems that I'm the only one asking for this feature, so no worries.

I will update this comment by the end of the month!

2024/05/01: due to some major personal setbacks, I won't assign myself another deadline. It's still very much possible that I do the whole thing on a whim sometime soon, though.

[LesFerch]

No problem. Thanks for the update!

[telgareith]

What about winget? It comes with windows.

[LesFerch]

What about winget? It comes with windows.

I recommend opening a new issue. I'll mark it as an enhancement and may look at it someday, but it would be nice to get some help to create a WinGet package.

The last time this came up, a user created a WinGet package for WinSetView following the guidelines for a portable app and there was an issue. Those guidelines apparently required the use of a symlink instead of a shortcut. But a symlink won't work correctly from a Cmd or PowerShell prompt. It works fine when double-clicked or executed via the Run menu. If this is accurate, I think it was a very silly idea for the powers that be to insist on a symlink. If they still have that requirement, then a WinGet package for WinSetView (and any portable app you wish to run from the command line) will be at least partially broken.

[telgareith]

I'll look into this when I can. Ironically- I have health issues that take precedence. But, I also have my own application that I need to publish asap. (I think I already missed the boat)