Skip to content
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.

kpm pack should also nupkg the project dependencies #80

Closed
loudej opened this issue Apr 4, 2014 · 1 comment
Closed

kpm pack should also nupkg the project dependencies #80

loudej opened this issue Apr 4, 2014 · 1 comment

Comments

@loudej
Copy link
Contributor

loudej commented Apr 4, 2014

After copying the source projects to the target location.

Do the k build on the source projects to generate the nupkg for each. Source packages should be built innermost-first from a dependency standpoint.

Expand those newly built nupkgs into the target packages folder. These expanded packages must be favored over the source project when calculating dependency versions.

@davidfowl davidfowl added this to the Post Alpha milestone Apr 17, 2014
@davidfowl davidfowl changed the title k pack should also nupkg the project dependencies kpm pack should also nupkg the project dependencies May 24, 2014
@lodejard
Copy link
Contributor

@glennc this is one of the two features we just talked about, actual implementation may be different than what is described, but in general it's the ability for a source project in the input to kpm pack becomes a package project in the output

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants