Embedding Paket into the template

[theimowski]

When #101 is ready, this would mean no longer dependency on full .NET / Mono

fsprojects/Paket#3183

[isaacabraham]

Does this mean no more mono is now needed?

[theimowski]

Yes, when paket works on .net core

[theimowski]

Paket 5.182.0-alpha001 comes with full .net core support - I'll start testing it with SAFE template

[theimowski]

@matthid when invoking fake as global tool it uses paket to restore the packages - does it look for paket in path? Does it mean that if you have paket installed as global tool, SAFE template doesn't need to provide a paket bootstrapper anymore?

[matthid]

@theimowski no. fake references paket.core and has no dependency on paket.exe

[theimowski]

Doh, right I forgot about that! This actually means that SAFE template doesn't have any dependency on Paket to spin up the template - we can just remove .paket/paket.exe (magic bootstrapper) completely. Then it's up to the user how one wants to call paket.
Or is there something I'm missing?

[theimowski]

So seems current situation is that thanks to FAKE 5, SAFE Template doesn't really need to bundle paket / paket.bootstrapper.
The question is whether we want to remove it altogether and let users choose their way of incorporating Paket into the project, or do we want to emphasise a solution, ideally based on .net core build of Paket?
I'm interested what people say @isaacabraham @forki @Krzysztof-Cieslak