chocolatey
Enhance the nuspec - second wave (enables fully declarative package manifests)
- 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
Also be sure to review https://github.com/chocolatey/choco/issues/205#issuecomment-115432181
This might also be able to handle https://github.com/chocolatey/choco/issues/278
One more thing which can be considered with this is to add a way to specify InstallArguments in a chocolatey dependency (To allow installation of a dependency like through an individual choco install VisualStudio2013Professional -InstallArguments "/Features:'WebTools Win8SDK' /ProductKey:AB1CD-EF2GH-IJ3KL-MN4OP-QR5ST" call)
@pascalberger That is big enough to warrant it's own issue. How do you verify that the dependency was installed with those arguments in the first place (if it is already installed). What actions should choco take if it is not installed with those args? It's not a small issue to overcome, so I see it as it's own discussion item.
@ferventcoder : any chance to get that feature soon? Would be great, as this is currently blocking an internal proof-of-concept to move to chocolatey to distribute VS
Hey @ferventcoder, any news about this?
I'm currently having problems with "choco pack", after replacing the <iconUrl> nuspec element with <icon>, as per Microsoft's suggestion.
@louis-z There are no plans at the moment as to when this would be implemented.
The Chocolatey Nuspec only supports <iconUrl>.
It would be nice to have an element to specify if the automatic uninstaller should be run. It was mentioned as an idea in this issue: https://github.com/chocolatey/choco/issues/2779#issue-1323424387
@louis-z There are no plans at the moment as to when this would be implemented.
The Chocolatey Nuspec only supports
<iconUrl>. @pauby I don't think anyone here is looking for anything from Choco other than flagging<icon>tags as errors as they are part of the nuspec.
Additionally, I know when using the icon tags, sleet and chocolatey gui, Icons work perefectly.
Any update on not flagging icon as an error? I can submit a PR, it is pretty simple edit.
PR's are welcomed. However, to set expectations, we are slow to review and merge.