Target specific feeds against specific dependencies

[isaacabraham]

The current implementation looks at e.g. all nuget sources across all nuget dependencies e.g.: -

source http://nuget.org/api/v2
source http://myprivatefeed
source http://myotherprivatefeed

nuget My.Package1
....
nuget My.Package24
nuget My.Package25

In the example above, My.Package24 goes against "privatefeed" and My.Package25 against "myprivatefeed". However, there is no way to indicate that in the dependencies file. As a result, updates etc. for any given package search across all feeds. It would be great if you could do something like: -

source http://nuget.org/api/v2
nuget My.Package1
....
nuget My.Package23

source http://myprivatefeed
nuget My.Package24

source http://myotherprivatefeed
nuget My.Package25

Where only packages 1-23 are searched against nuget.org, My.Package24 against myprivatefeed and My.Package25 against myotherprivatefeed.

[forki]

yep I thought this will come back one day.

This is only because of performance, right? Otherwise the current stuff would be OK.

// @agross @ilkerde

[isaacabraham]

Yep. Unless there was a dependency that existed in two feeds and you wanted to explicitly only one feed I suppose.

[forki]

yes but then it should be the exact same package (modulo monkey-patching ;-) )

[isaacabraham]

why - if you uploaded a newer version to one feed than another one?

[forki]

That's different version no. then, right?
On Nov 3, 2014 7:37 PM, "Isaac Abraham" [email protected] wrote:

why - if you uploaded a newer version to one feed than another one?

—
Reply to this email directly or view it on GitHub
#331 (comment).

[isaacabraham]

Yes, exactly :-)

[mexx]

Currently the order of sources defines the source that will be used in a situation where same package in same version is present in different feeds.

Unfortunately currently the source to use is picked when details of the package gets fetched and not when the available versions are determined.
It could possibly happen that a version that would be not available in first feed at time of version resolution and available in second feed, but when details get fetched that version would be already in first feed and this package would be downloaded.

Note:
With feed specific dependencies comes a problem, what feed the indirect dependencies should be resolved from. To resolve this problem we have to define an order for the sources to proceed. With that we have something like sources dependencies tree.

[isaacabraham]

In terms of performance, I moved a single package (out of about 20 dependencies) from a secondary nuget feed to a local file system feed. The time to do a paket update went down from about 5 minutes to 30 seconds.

[forki]

Ok I think this is something to do next.

We should work towards a grouping feature.
/cc @agross

[agross]

Grouping is for dev vs production dependencies. While I agree that that's not usual in the .NET space I'd prefer something like this:

source http://teamcity/feed username: "blah" password: "secret" do
  nuget foobar ~> 1.2
end

[forki]

Closing old issue. This can be done via groups