Add metadata to enhance the Chocolatey `.nuspec` file
- Dominant language
- C#
- Stars
- 11.5k
- Forks
- 960
- PR merge metrics
- No merged PRs in 30d
Description
- original software version string
- supportUrl
- chatUrl
This catches more of the enhancements noted at https://github.com/chocolatey/chocolatey.org/issues/101 :
- ARP Name (with wildcard support) (software Name)
- Software Display Version
- OS versions
- Architectures
- Languages supported
- Silent options - all options supported
- Installer type (can help provide silent options)
- Package specific execution timeout - see #963
Other things that can be added:
- Installer url
- Installer 64 bit url
- installer checksum / checksum x64
- checksumtype / checksumtype x64
- Sanitising package ID (see https://github.com/NuGet/Announcements/issues/75)
Also be sure to review https://github.com/chocolatey/choco/issues/205#issuecomment-115432181
Contributor guide
Research direction
Start by tracing how the Chocolatey .nuspec file is generated, then review the linked chocolatey.org, NuGet, and choco discussions to separate the requested metadata from the additional suggestions. Done means the agreed metadata is represented in the generated package description and covered by the repository's existing validation or packaging checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100