Suggestions for Improving Package Management in winget

[mcexit]

Suggestions for Improving Package Management in winget

Addressing Deprecated and Unmaintained Packages

I've noticed several packages in this repository are deprecated, no longer functional, or maintained. Examples include:

• Google.Talk
• Google.Desktop
• Soon to be deprecated: Google.VPNByGoogleOne

These packages should be moved to a new archive remote to keep the main repository clean and functional.

---

Enhancing Package Search and Categorization

Searching for Free (Open-Source) Packages

Currently, there's no easy way to filter for only free or open-source packages. This is a crucial feature for users who prefer or require open-source software.

Separating Beta, Canary, Alpha, and Stable Releases

When searching with winget, beta, canary, alpha, and stable releases are shown together. These should be separated to improve user experience. Possible solutions include:

• Different remotes for different release types
• CLI flags to filter results
• Different branches and repos for each package

Examples of Repository Structure

To improve maintainability and usability, consider organizing the repository into separate folders that could act as remotes. Examples could include:

• Free Packages: free/main, free/testing, free/community
• Open-Source Packages: open-source/main, open-source/testing
• Non-Free Packages: non-free/main, non-free/testing
• Archived Packages: archived/free/main

---

Metadata and Maintenance

Importance of Metadata

Maintaining accurate metadata is crucial. For instance, having manifest fields for ReleaseDate can help identify unmaintained packages. This allows winget to sort packages by release date, aiding in the identification of outdated software.

Core Maintainers and Package Review

Reserving main or core for packages reviewed and published by core maintainers ensures a high standard of quality and reliability. This distinction helps users trust the software they install.

---

Benefits of Structured Repository

Organizing the repository as suggested:

• Improves Maintainability: Clear structure aids in long-term maintenance.
• Encourages Contributions: Contributors can easily find and work on packages they care about.
• Enhances User Experience: Users can filter and find the software they need more efficiently.
• Facilitates Better Management: A well-organized structure helps in better tracking and updating of packages.

---

Conclusion

I'm enthusiastic about winget, especially with my background in Linux package management. However, the current all-in-one approach may not be sustainable long-term. While abstraction is a possible solution, it may alienate users looking for a common open-source approach. Therefore, adopting a structured repository with clear categorization and metadata seems like an ideal approach.