Declaring dependency on packages from alternate sources

[jberezanski]

I'd like to be able to specify in the nuspec a dependency on a package from one of the alternate sources, in particular WindowsFeatures or WebPI.

For example:

<dependency id="IIS-WebServer" source="WindowsFeatures" />
<dependency id="WDeploy36" source="WebPI" />

[ferventcoder]

I'm surprised there isn't already an issue created for this?

[jberezanski]

I did not find anything, not even in the old chocolatey repo.

[ferventcoder]

This is one of those things where almost all of NuGet packaging will need to be integrated into Chocolatey's codebase. Since the concept of alternate sources is foreign to NuGet.Core at this time, I'm pushing this out to 1.x or 2.x

[ferventcoder]

There has been a lot of discussion on this, that's why it is surprising.

[dragon788]

This could be sweet. Current workaround is probably using a Boxstarter script or custom ps1 to do all the choco calls, but native would be awesome especially for installing VisualStudio and various Vsix plugins.

[ferventcoder]

VSIX and VisualStudio is already supported as packages.

[jberezanski]

If it were implemented, I would probably craft a new "Windows Update" source, which could eliminate the burden of creating KB packages.

[dragon788]

Boxstarter already includes a Windows Update capability, perhaps build on that? I know it has some options for specifying/ignoring updates so maybe could target specific KBs.

On Dec 2, 2016 2:19 AM, "Jakub Berezanski" notifications@github.com wrote:

If it were implemented, I would probably craft a new "Windows Update" source, which could eliminate the burden of creating KB packages.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/chocolatey/choco/issues/879#issuecomment-264398594, or mute the thread https://github.com/notifications/unsubscribe-auth/AAdxXoQcnFiG2RY6xu4jU4y3CTRmOL8Rks5rD9R4gaJpZM4JWiQ6 .

[jarl-haggerty]

Any update on this? I was trying to create a dependency on NetFx3 in windowsfeatures.

[ferventcoder]

@jarl-haggerty not yet - this requires more invasive changes to the nuspec format. It has a milestone attached to it, and as you might see that is 2.x. We are still in the works for 1.x

[ferventcoder]

You can simply create a package for now for netfx3. Also keep in mind to do what you would like, we would need to take into consideration that we'd need os grouped dependencies as the feature names can change in different OS versions (from Windows Features / DISM).

[lukasz-mitka]

As a user I find it ridiculous I have to go over Description to confirm the package doesn't have some non-automatic dependencies and then install them manually. I understand there's a workaround but it creates unnecessary work and packages.

[gep13]

@lukasz-mitka just to make sure that we are talking about the same thing here... can you provide an example of a package where this is currently the case?

Thanks

[lukasz-mitka]

@gep13 Here: https://community.chocolatey.org/packages/docker-engine You can even see author tried to get it to work: https://github.com/AJDurant/choco-docker-engine/blob/main/docker-engine.nuspec#L41