-
Notifications
You must be signed in to change notification settings - Fork 905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Icons on fileshare repo #2592
Comments
@barjonas Chocolatey forked the nuspec format that is used, so we don't follow along exactly with what NuGet.exe (the link that you provided does), so just because The ability to support embedded icons in a package is definitely something that we want to have, but as you say, this is something that will require changes both from a repository (community.chocolatey.org) stand point, as well as within choco.exe as well. We have a tracking issue regarding the upgrade to the latest NuGet assemblies, which will likely encompass the ability to use embedded icons: Can I suggest that you follow that issue for updates on this. For now, I am going to close out this issue. @ryanrichter94 this is another example of why we need this: chocolatey/docs#374 |
Embedded icons are not supported. There is no timescale for when it will be implemented. |
I'm starting on my Chocolatey journey by using a shared directory as a repository. I have an install script which adds this repository using an environment variable and build scripts which push to the repository in the same way. The literal URL could end up varying between machines. This does not appear to leave any option for hosting icons.
<iconUrl>
does not support relative paths. That element is deprecated in the latest nuspec spec anyway, but choco does not appear to support the newer<icon>
element. If it did, it could be a great solution to my particular scenario.I can see how this would add complexity to the tooling. The web repository would have to know how to maintain its own cache, and each client probably would too. But, on the other hand, part of the attraction to a package manager is their self-contained nature. This would make for more deterministic behavior than relying on multiple external CDNs etc. It would also make the documentation much simpler.
The text was updated successfully, but these errors were encountered: