-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Add chocolatey dependency type #24
Comments
Maybe supporting DSC as a Dependency type via
The advantage is that it allows to then extending the Dependency Types by proxying the DSC Dependency type (i.e. creating a Choco dependency type by proxying the DSC Dependency type on the Choco DSC resource). Thus leveraging all the existing DSC Resources... Maybe a fully fledged DSC dependency can be created using the LCM (hence supporting Composite resource), but that sounds a bit more work. |
So! If we end up creating a chocolatey dependency type, I'm inclined to include a test/bootstrap bit in the dependency script. Given that folks can preload (we'll include a param for path that defaults to choco command resolution path), any concern simply calling the standard install script in the off case a bootstrap is needed? |
Good idea, but I think that script is missing 1 feature: a configurable Nuget server (say you want to install from a local feed, and retrieve the latest versions). for other functions, I wrote a few here that could help out: https://github.com/gaelcolas/PackageProviderBootstrap/tree/master/PackageProviderBootstrap/public |
FWIW, I re-wrote the Install script and that module for Chocolatey + DSC here: https://github.com/gaelcolas/Chocolatey/ So to bootstrap you could use At that point, I wonder if it's not worth implementing a DSC Dependency type instead, so that could just use this chocolatey module directly...? |
Thinking of this way, way late, but @ferventcoder might have thoughts on this. |
We support PackageManagement, but, that's not exactly recommended over choco.exe at the moment.
The text was updated successfully, but these errors were encountered: