Fable 2 and paket about fable-templates

[enricosada]

Florian, global tool installed + hook is exactly how will work. The hook work really well, no paket.exe in repo and `dotnet build` from clone works. You can try it in https://github.com/enricosada/paket-netcore-testing-as-tool/blob/master/README.md#scenario-2-integration-with-sdk The issue atm is paket .net core doesn't respect the web proxy. It's the only big issue I know (and is the same issue you'll get install with dotnet install). Happy to get help with that, otherwise I'll do it but in free time this weekend I hope From mobile

-- Enrico Sada @enricosada

________________________________ From: Steffen Forkmann <[email protected]> Sent: Wednesday, October 3, 2018 9:46:40 PM To: fable-compiler/fable-templates Cc: Enrico Sada; Mention Subject: Re: [fable-compiler/fable-templates] Fable 2 and paket (#16) Yes global tools exist as well. But I'm hoping for repo tools. But maybe I'm just a dreamer Florian Verdonck <[email protected]> schrieb am Mi., 3. Okt. 2018, 20:25:

Currently these Tools are project specific as in fsproj Not true, the new global cli (netcore 2.1) can be installed in a local folder. dotnet tool install --tool-path \".paket\" Paket --version 5.182.0-alpha001 --add-source https://api.nuget.org/v3/index.json" Will literally install a paket.exe (or a paket file on Linux) into a .paket folder. No fsproj is touched by this. So from there on everything is the same as it used to be. The suggestion here is to remove the (mono compatible) paket.exe <https://github.com/fable-compiler/fable-templates/tree/master/simple/Content/.paket> and install the latest (netappcore2.1) version with a hook. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNHvOmP6m4ryEK_9AW8-zfjdU7YXnks5uhQEDgaJpZM4XF23L> .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#16 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAI_K_e_fVL-wpHQT_VEDpUglDqi4lLOks5uhRQggaJpZM4XF23L>.

[alfonsogarciacaro]

I'd love to remove the Mono dependency, although I'm still wary of the new local cli tools because it seems the current design is not final yet. Not sure, any thoughts on this? @MangelMaxime @forki @enricosada

[MangelMaxime]

I'm still wary of the new local cli tools because it seems the current design is not final yet

I do agree, I think waiting for the final design could be a good thing. But I am no expert of what is related to dotnet :) So I will follow the decision of @forki and @enricosada as they are probably more inform on this subject.

[forki]

/cc @enricosada I think we need to wait for project wide tools. Maxime Mangel <[email protected]> schrieb am Mi., 3. Okt. 2018, 14:58:

…

I'm still wary of the new local cli tools because it seems the current design is not final yet I do agree, I think waiting for the final design could be a good thing. But I am no expert of what is related to dotnet :) So I will follow the decision of @forki <https://github.com/forki> and @enricosada <https://github.com/enricosada> as they are probably more inform on this subject. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNNnON0N5eqhOPdlxdR-eMf0Id1Vcks5uhLRWgaJpZM4XF23L> .

[nojaf]

@forki, could please elaborate? What do you mean with project wide tools?

[forki]

Currently these Tools are project specific as in fsproj. But we need them to be repository wide Florian Verdonck <[email protected]> schrieb am Mi., 3. Okt. 2018, 17:32:

…

@forki <https://github.com/forki>, could please elaborate? What do you mean with project wide tools? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNNgSwFxoBQEwzwu-t6s6ojMTO5H6ks5uhNiigaJpZM4XF23L> .

[nojaf]

Currently these Tools are project specific as in fsproj

Not true, the new global cli (netcore 2.1) can be installed in a local folder.

dotnet tool install --tool-path \".paket\" Paket --version 5.182.0-alpha001 --add-source https://api.nuget.org/v3/index.json"

Will literally install a paket.exe (or a paket file on Linux) into a .paket folder.
No fsproj is touched by this.
So from there on everything is the same as it used to be.

The suggestion here is to remove the (mono compatible) paket.exe and install the latest (netappcore2.1) version with a hook.

[forki]

Yes global tools exist as well. But I'm hoping for repo tools. But maybe I'm just a dreamer Florian Verdonck <[email protected]> schrieb am Mi., 3. Okt. 2018, 20:25:

…

Currently these Tools are project specific as in fsproj Not true, the new global cli (netcore 2.1) can be installed in a local folder. dotnet tool install --tool-path \".paket\" Paket --version 5.182.0-alpha001 --add-source https://api.nuget.org/v3/index.json" Will literally install a paket.exe (or a paket file on Linux) into a .paket folder. No fsproj is touched by this. So from there on everything is the same as it used to be. The suggestion here is to remove the (mono compatible) paket.exe <https://github.com/fable-compiler/fable-templates/tree/master/simple/Content/.paket> and install the latest (netappcore2.1) version with a hook. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNHvOmP6m4ryEK_9AW8-zfjdU7YXnks5uhQEDgaJpZM4XF23L> .

[alfonsogarciacaro]

Local tools should be more or less the same as repo tools, the main problem right now is there's no easy way to manage the version. Seems MSFT is working on this, more info here.

[enricosada]

As a note, the proposed already allow to pin paket version (best practice). If someone can fix web proxy From mobile

-- Enrico Sada @enricosada

________________________________ From: Enrico Sada Sent: Wednesday, October 3, 2018 10:20:04 PM To: fable-compiler/fable-templates; fable-compiler/fable-templates Cc: Mention Subject: Re: [fable-compiler/fable-templates] Fable 2 and paket (#16) Florian, global tool installed + hook is exactly how will work. The hook work really well, no paket.exe in repo and `dotnet build` from clone works. You can try it in https://github.com/enricosada/paket-netcore-testing-as-tool/blob/master/README.md#scenario-2-integration-with-sdk The issue atm is paket .net core doesn't respect the web proxy. It's the only big issue I know (and is the same issue you'll get install with dotnet install). Happy to get help with that, otherwise I'll do it but in free time this weekend I hope From mobile

-- Enrico Sada @enricosada

________________________________ From: Steffen Forkmann <[email protected]> Sent: Wednesday, October 3, 2018 9:46:40 PM To: fable-compiler/fable-templates Cc: Enrico Sada; Mention Subject: Re: [fable-compiler/fable-templates] Fable 2 and paket (#16) Yes global tools exist as well. But I'm hoping for repo tools. But maybe I'm just a dreamer Florian Verdonck <[email protected]> schrieb am Mi., 3. Okt. 2018, 20:25:

Currently these Tools are project specific as in fsproj Not true, the new global cli (netcore 2.1) can be installed in a local folder. dotnet tool install --tool-path \".paket\" Paket --version 5.182.0-alpha001 --add-source https://api.nuget.org/v3/index.json" Will literally install a paket.exe (or a paket file on Linux) into a .paket folder. No fsproj is touched by this. So from there on everything is the same as it used to be. The suggestion here is to remove the (mono compatible) paket.exe <https://github.com/fable-compiler/fable-templates/tree/master/simple/Content/.paket> and install the latest (netappcore2.1) version with a hook. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNHvOmP6m4ryEK_9AW8-zfjdU7YXnks5uhQEDgaJpZM4XF23L> .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#16 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAI_K_e_fVL-wpHQT_VEDpUglDqi4lLOks5uhRQggaJpZM4XF23L>.

[enricosada]

And repo tool (mentioned by Forki) are just a way to pin the version of tool in paket, who install it with `dotnet install` to a specific dir. Plus install of `tool/*.exe` for .net old packages, not packages as global tools. This need a rebase, is in a PR, todo after netcore in my backlog From mobile

-- Enrico Sada @enricosada

________________________________ From: Enrico Sada Sent: Wednesday, October 3, 2018 10:21:10 PM To: fable-compiler/fable-templates; fable-compiler/fable-templates Cc: Mention Subject: Re: [fable-compiler/fable-templates] Fable 2 and paket (#16) As a note, the proposed already allow to pin paket version (best practice). If someone can fix web proxy From mobile

-- Enrico Sada @enricosada

________________________________ From: Enrico Sada Sent: Wednesday, October 3, 2018 10:20:04 PM To: fable-compiler/fable-templates; fable-compiler/fable-templates Cc: Mention Subject: Re: [fable-compiler/fable-templates] Fable 2 and paket (#16) Florian, global tool installed + hook is exactly how will work. The hook work really well, no paket.exe in repo and `dotnet build` from clone works. You can try it in https://github.com/enricosada/paket-netcore-testing-as-tool/blob/master/README.md#scenario-2-integration-with-sdk The issue atm is paket .net core doesn't respect the web proxy. It's the only big issue I know (and is the same issue you'll get install with dotnet install). Happy to get help with that, otherwise I'll do it but in free time this weekend I hope From mobile

-- Enrico Sada @enricosada

________________________________ From: Steffen Forkmann <[email protected]> Sent: Wednesday, October 3, 2018 9:46:40 PM To: fable-compiler/fable-templates Cc: Enrico Sada; Mention Subject: Re: [fable-compiler/fable-templates] Fable 2 and paket (#16) Yes global tools exist as well. But I'm hoping for repo tools. But maybe I'm just a dreamer Florian Verdonck <[email protected]> schrieb am Mi., 3. Okt. 2018, 20:25:

Currently these Tools are project specific as in fsproj Not true, the new global cli (netcore 2.1) can be installed in a local folder. dotnet tool install --tool-path \".paket\" Paket --version 5.182.0-alpha001 --add-source https://api.nuget.org/v3/index.json" Will literally install a paket.exe (or a paket file on Linux) into a .paket folder. No fsproj is touched by this. So from there on everything is the same as it used to be. The suggestion here is to remove the (mono compatible) paket.exe <https://github.com/fable-compiler/fable-templates/tree/master/simple/Content/.paket> and install the latest (netappcore2.1) version with a hook. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNHvOmP6m4ryEK_9AW8-zfjdU7YXnks5uhQEDgaJpZM4XF23L> .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#16 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAI_K_e_fVL-wpHQT_VEDpUglDqi4lLOks5uhRQggaJpZM4XF23L>.

[nojaf]

I see, so scenario two does seem to hit the sweet spot.
I've tried it in my own sample project and it works out nicely.

[nojaf]

Closing this issue as simple fable package doesn't have paket anymore.
It is easy to install .NETCore paket and run paket convert-from-nuget.