chocolatey-licensed-issues
chocolatey-licensed-issues copied to clipboard
chocolatey
Allow overriding download url (which helps in the case of bad download locations)
This would make @rismoney so happy!
Also downloadUrlx64 so if you want to point to both.
If you only provide the first, it will use it no matter what. If you provide both, it will select by architecture.
I looked over in chocolatey/chocolatey to find the old issue that mentioned this, but maybe it was just in email threads and/or discussion on other issues over on chocolatey/chocolatey.
This would make @rismoney so happy!
The particular use case is this-
All my package binaries are currently fetching from an internal repo say: chocopackages.rismoney.com This makes all those packages non-portable. I would like to put in the URL a token, and have chocolatey insert the hostname location.
this way i could code all my packages w/o using chocopackages.rismoney.com and instead use the token.
This would go a long way towards open sourcing our packages, and have people be able to use them on their internal repos w/o modifying the chocolateyinstall.ps1 for their org.
Rismoney, wouldn't you be able to do what you are currently describing using the PackageParameters input to the choco install/upgrade commands?
yes, but the key is i don't want to specify it on the command line. i imagine it could be contained within the xml config file.
Can I use this with Chocolatey's feed? I'm having trouble with Fosshub links.
And yes, being able to set this in a config file would be nice.
@rismoney said... but the key is i don't want to specify it on the command line.
Ah, I see what you are getting at. I like that idea, but I would see that as a separate issue to this one, which allows overriding of the URL. Great idea!
@i-give-up this is just an issue to track the work that needs to be done, and hasn't yet been implemented, but yes, the idea would be that you could use it on any package, regardless of where it is hosted.
@rismoney @gep13 yes, that is more about something businesses would take advantage of. :)
This is going to be a trickle down feature, first available in pro+ editions and later available in open source.