paket init should pin itself

[manne]

Description

paket.exe init should pin the version of itself into paket.dependencies

Scenario

Given paket.exe is available in version 1.2.3
When one wants to initialize its repository
Then paket.exe init is called

Expected behavior

The command generates paket.dependencies file with this content

version 1.2.3
source https://www.nuget.org/api/v2

Actual behavior

The command generates paket.dependencies file with this content

source https://www.nuget.org/api/v2

Two possibilities
A. Introduce an option, e.g. --pin. The behavior is backward compatibility.
B. Make it as the standard behavior. The behavior is a "breaking change"

I prefer B, because one of the many advantage of paket is pinning the version of the (transitive) dependencies. So it is only logical to pin the version of paket itself.

I can submit a PR.

[manne]

@matthid here you go 😏

[matthid]

I think it's reasonable.

[manne]

@matthid which possibility do you prefer?

[matthid]

Honestly I'd go for B.
In fact I think this might introduce some problems for new people where they will never notice that they need an update. To compensate for this I feel like paket update should update its own version. But I have that opinion for ages ;)

[forki]

We would love to see a PR for that. Matthias Dittrich <notifications@github.com> schrieb am Di., 31. Juli 2018, 19:29:

…

Honestly I'd go for B. In fact I think this might introduce some problems for new people where they will never notice that they need an update. To compensate for this I feel like paket update should update its own version. But I have that opinion for ages ;) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3320 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNIht4DIlDCQD7wJOeS4ukfDp8ZBoks5uMJPpgaJpZM4VojOF> .

[manne]

Option A or B?