Skip to content

Updated FsBlog.nuspec so that Paket will be included in the NuGet package.#34

Open
GradientVector wants to merge 3 commits intofsprojects:masterfrom
GradientVector:Fix-Nuget-Package
Open

Updated FsBlog.nuspec so that Paket will be included in the NuGet package.#34
GradientVector wants to merge 3 commits intofsprojects:masterfrom
GradientVector:Fix-Nuget-Package

Conversation

@GradientVector
Copy link

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?

…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?
@cdrnet
Copy link
Member

cdrnet commented Feb 6, 2015

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?
@GradientVector
Copy link
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.

@tpetricek
Copy link
Member

@MattDrivenDev @cdrnet @nelak Could any of you guys check the updated PR, merge it & release a new package?

@cdrnet
Copy link
Member

cdrnet commented Apr 8, 2015

@tpetricek I can check and pull the PR, but I do not have the credentials to release a new NuGet package.

@nelak
Copy link
Collaborator

nelak commented Apr 8, 2015

@cdrnet Do you have a nuget account? I can add you as owner of the package

@cdrnet
Copy link
Member

cdrnet commented Apr 14, 2015

@nelak thanks, that worked

@forki
Copy link
Member

forki commented Nov 11, 2015

can this be closed?

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.

5 participants