Skip to content
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

Do not add development dependencies to the nuspec of a target nupkg while paket packing #3873

Conversation

ruhullahshah
Copy link
Contributor

Motivation:

It was observed on some systems that paket pack adds development dependencies to the nuspec of a target nuget package.
The root cause for this has been documented here. This PR aims to fix issue #3723

Description of fix:

If a nupkg does not exist in the local nuget cache, try to load the nuspec from the DefaultPackagesFolder before returning a Nuspec.All

…cache, then we return a Nuspec.All

which even causes development dependencies to be added to the resultant nuspec and is not correct behavior.

This can be remedied by searching for the dependency in the DefaultPackagesFolder before giving up and using Nuspec.All.
This change intoduces this methodology.
@ruhullahshah ruhullahshah changed the title Do not add developmentDependencies to target nuspec while paket packing Do not add development dependencies to the nuspec of a target nupkg while paket packing Jun 26, 2020
@forki forki merged commit dc039e8 into fsprojects:master Jun 27, 2020
@forki
Copy link
Member

forki commented Jun 27, 2020

thanks a lot for taking care of this

@ruhullahshah
Copy link
Contributor Author

You are welcome

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

Successfully merging this pull request may close these issues.

None yet

2 participants