Updated FsBlog.nuspec so that Paket will be included in the NuGet package.#34
Open
GradientVector wants to merge 3 commits intofsprojects:masterfrom
Open
Updated FsBlog.nuspec so that Paket will be included in the NuGet package.#34GradientVector wants to merge 3 commits intofsprojects:masterfrom
GradientVector wants to merge 3 commits intofsprojects:masterfrom
Conversation
…kage. As it stands right now, running ``nuget pack FsBlog.nuspec`` results in a NuGet package which does not include Paket. Running ``fake`` from the NuGet package fails because there is no .paket directory with paket.exe or paket.bootstrapper.exe. Due to a bug (feature?) of ``nuget pack``, copying of files or directories which begin with a dot is troublesome. I added Paket as a dependency so that I could copy it from the packages directory instead. Also updated the NuGet version number. Perhaps it is time to upload a new package to nuget.org?
Member
|
Would it be possible to include the paket bootstrapper only, instead of paket.exe itself? |
Also added paket.targets file. == From Previous commit message Updated FsBlog.nuspec so that Paket will be included in the NuGet package. As it stands right now, running ``nuget pack FsBlog.nuspec`` results in a NuGet package which does not include Paket. Running ``fake`` from the NuGet package fails because there is no .paket directory with paket.exe or paket.bootstrapper.exe. Due to a bug (feature?) of ``nuget pack``, copying of files or directories which begin with a dot is troublesome. I added Paket as a dependency so that I could copy it from the packages directory instead. Also updated the NuGet version number. Perhaps it is time to upload a new package to nuget.org?
Author
|
Included paket.bootstrapper.exe and paket.targets in the tools folder. I am not sure if that is the best place in source, but the generated NuGet package is correct. |
Member
|
@MattDrivenDev @cdrnet @nelak Could any of you guys check the updated PR, merge it & release a new package? |
Member
|
@tpetricek I can check and pull the PR, but I do not have the credentials to release a new NuGet package. |
Collaborator
|
@cdrnet Do you have a nuget account? I can add you as owner of the package |
Member
|
@nelak thanks, that worked |
Member
|
can this be closed? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As it stands right now, running
nuget pack FsBlog.nuspecresults in a NuGetpackage which does not include Paket. Running
fakefrom the NuGet packagefails because there is no .paket directory with paket.exe or
paket.bootstrapper.exe.
Due to a bug (feature?) of
nuget pack, copying of files or directories whichbegin with a dot is troublesome. I added Paket as a dependency so that I could
copy it from the packages directory instead.
Also updated the NuGet version number. Perhaps it is time to upload a new
package to nuget.org?