-
Notifications
You must be signed in to change notification settings - Fork 520
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
Support developmentDependency nuget dependencies #796
Comments
I think I found a bit of docs at http://docs.nuget.org/Release-Notes/NuGet-2.7#development-only-dependencies. So if I understand correctly we would need to understand the flag in dependent packages and just exclude it from the generated nuspec for the new package!? /cc @adamralph |
regarding |
I started to work on the feature |
this is not part of the nuget odata, right? |
This is where they originally implemented it: http://nuget.codeplex.com/workitem/1956 |
I only implemented the part that we exclude these dependencies from the new nuget package. Please test it. |
@forki yep, that's the correct assumption. It just tells you whether or not to include the package as a dep when creating a package from your project. |
yeah, but it's really unfortunate that the data is missing in the OData metadata. It breaks our default assumption that we can look this stuff up while running update. Now we need to look into the nuspec which can only do after downloading the package. |
fugly 😢 |
Bit late for my feedback, but it works, thanks :) |
I just converted an existing project from Nuget to paket.
This project had a dependency on https://github.com/damianh/LibLog, which is a developmentDependency
When I produce a nuget package of the project, it includes LibLog as a regular dependency, while it should actually add no dependency to it.
Does paket support defining that a certain nuget package is a developmentDependency so it will not get included in the resulting nuspec from
paket pack
?The text was updated successfully, but these errors were encountered: