Add an extension point to paket pack to specify dependancies by framework

[enricosada]

to make it possibile to support dependencies by framework (like .NET Core) until #913 is ready

I think two command line arguments are enough, it's a temporary but can help a lot, and low regression (replacement/addition are done after nuspec is generated)

an example:

• paket pack --defaultgroup net40 to put generated nuspec deps inside a group

• paket pack --additionaldeps "path/to/file" and path/to/file contains the other groups in nuspec format

   <group targetFramework="DNXCore5.0">
      <dependency id="Microsoft.FSharp.Core.netcore" version="[1.0.0-alpha-151221, )" />
      <dependency id="NETStandard.Library" version="[1.0.0-rc2-23811, )" />
    </group>
  

[forki]

mhm. can you come up with a syntax for paket.template instead?

[enricosada]

I dont know enough about resolution and backward compatibility to comment about paket.template syntax.
I know that's an hack, i was trying to find something safe and easy to implement
But maybe it's better to wait template support, more clean, i'll close

[forki]

Let's keep it open for discussion. I will revisit soon

[enricosada]

Dunno, probably that's not the best way, or is not ok. For sure is an hack

It's a bit selfish, but i just need something to add .NET Core framework to nuget packages created with paket pack that's my problem.
Root cause is #913 but i dont know how much work is that, and this can be wasted work
Atm is really an hack ( ref chessie fsprojects/Chessie@eef358e ) for dependencies ( unzip nuspec from nupkg, modify nuspec xml, zip back ). files are ok

Maybe some way to change the nuspec before the nupkg is created is ok too.

I can add the hack in FAKE as target, but not everyone who use paket use fake too, so it's a annoying

[enricosada]

Closing. paket.template support that