[Update Request]: SomePythonThings.WingetUIStore

[Strong-pwned]

What type of update are you requesting?

A change to the Package Identifier

Current Package Identifier

SomePythonThings.WingetUIStore

Package Version

All

Please describe the changes you would like to see

Suggested new package identifier:
MartiCliment.UniGetUI

Motivation:

• The official publisher and author of the app is Martí Climent, not "SomePythonThings".
• The official name of the app is UniGetUI, not WingetUI.

Compatibility:
Anyone searching for the old name (winget search wingetui) will find the new name, since the package name and tags already have the old name:

winget-pkgs/manifests/s/SomePythonThings/WingetUIStore/3.1.1/SomePythonThings.WingetUIStore.locale.en-US.yaml

Line 11 in f490e2c

PackageName: UniGetUI (formerly WingetUI)

winget-pkgs/manifests/s/SomePythonThings/WingetUIStore/3.1.1/SomePythonThings.WingetUIStore.locale.en-US.yaml

Lines 30 to 31 in f490e2c

	- winget
	- winget-ui

Additional information:
Official repository (the app is written in C#, not Python):
https://github.com/marticliment/UniGetUI/
Official website (mentioned in the repository):
https://www.marticliment.com/unigetui/

This is referenced in the manifest file itself:

winget-pkgs/manifests/s/SomePythonThings/WingetUIStore/3.1.1/SomePythonThings.WingetUIStore.locale.en-US.yaml

Lines 7 to 16 in f490e2c

	Publisher: Martí Climent
	PublisherUrl: https://github.com/marticliment/UniGetUI
	PublisherSupportUrl: https://github.com/marticliment/UniGetUI/issues
	Author: Martí Climent
	PackageName: UniGetUI (formerly WingetUI)
	PackageUrl: https://github.com/marticliment/UniGetUI
	License: MIT
	LicenseUrl: https://raw.githubusercontent.com/marticliment/UniGetUI/main/LICENSE
	Copyright: Copyright (c) 2024 Martí Climent
	CopyrightUrl: https://raw.githubusercontent.com/marticliment/UniGetUI/main/LICENSE

[vikingnope]

@marticliment would you agree with this change, or would you suggest leaving it as is?

[marticliment]

Yes, it definitely makes sense to make the change

[vikingnope]

Should have probably added this to previous question but here goes:

@marticliment do you think we should:

1. Remove previous WingetUI in total and just create a manifest for UniGetUI
   OR
2. Keep WingetUI here and remove the UniGetUI manifests from it, and just create a new manifest for UniGetUI?

I think it honestly just depends if you want to keep the previous WingetUI branding or not

[marticliment]

Ideally it would be better to follow option 1, to prevent confusion, but I don't know if it is feasible and acceptable to delete an entire package and then publish it again with different names. Having that said, either if it ends up being option 1 or 2 it will be ok for me.

[vikingnope]

@stephengillie, would you suggest option 1 or 2 based on Marti's feedback and winget's terms?

[stephengillie]

I agree with @ marticliment that the first option is better. While it would be possible for us to continue offering WinGetUI as a historical record, I'm not sure how much demand there is for it.

A third possible option could be leaving the manifests before the name change as-is, and only moving the post-rename manifests. This could reduce workload while also preserving the older manifest versions.

Note

Moving packages from one PackageIdentifier to another can be a lot of work. Foreach manifest version, 2 PRs are needed - one to add new and one to remove old. This process always winds up having some level of coordination between the submitter and a moderator to approve, and with the appropriate preparation can go very smoothly.

[vikingnope]

I agree with @ marticliment that the first option is better. While it would be possible for us to continue offering WinGetUI as a historical record, I'm not sure how much demand there is for it.

A third possible option could be leaving the manifests before the name change as-is, and only moving the post-rename manifests. This could reduce workload while also preserving the older manifest versions.

Note

Moving packages from one PackageIdentifier to another can be a lot of work. Foreach manifest version, 2 PRs are needed - one to add new and one to remove old. This process always winds up having some level of coordination between the submitter and a moderator to approve, and with the appropriate preparation can go very smoothly.

So what I will do is follow what you suggested which is to create the new manifest then remove the old one. 😊

I don't think WingetUI is still in demand since most people always want the latest version, which in this case is UniGetUI

[vikingnope]

I will continue the rest when these commit just to make sure everything is correct

[marticliment]

Assuming we chose to delete the old manifests and just start from scratch (Option 1), would it be possible to delete all the manifests in one single PR? Or we'd still need to do one manifest at a time?

I don't think WingetUI is still in demand since most people always want the latest version, which in this case is UniGetUI

I agree, and all the installers for older versions are still (and will be) available on GitHub, so installing older versions shouldn't be an issue.

[vikingnope]

Assuming we chose to delete the old manifests and just start from scratch (Option 1), would it be possible to delete all the manifests in one single PR? Or we'd still need to do one manifest at a time?

They will have to be removed in separate PRs one-by-one but that is easy with Komac, the hardest part is transferring all of the UniGetUI manifests because they have to be done manually, luckily this was caught early on so not many versions... 😌

[marticliment]

Lots of thanks, @ vikingnope. I will be updating my workflow so new releases automatically point to the new package

[vikingnope]

When these are committed I will start removing all the packages from SomePythonThings.WingetUI

[vikingnope]

Multiple PRs have been scheduled so that this can be completed

[vikingnope]

Not entirely finished, still a bit more to go

[vikingnope]

This has officially been completed, I thank you all for your patience. :)