Seriously wondering why this wasn't suggested earlier.
I'm voting for option "3" which seems to be the easiest to implement.
IMHO we should not complicate the bootstrapper if we don't really need to. For example "1" could be integrated in the paket startup code instead or as suggested in 'paket outdated' (which I would prefer).

I have thought about it earlier and thought about paket.bootstrapper.exe --self
I came to that point when github had problems some time ago and we implemented an alternative nuget download. The only problem I had so far with that is that in the nuget package is no paket.bootstraper.

BTW you can copy it over the current bootstrapper.exe to self update

so we need a Paket.Boostrapper package?

@Stift what about the paket.targets file?

How do we know when to run the update command? every time? or is paket.exe outdated running this?

@forki in case we want a self update via nuget we could need one

@dnauck have not considered yet the paket.target file, but could be done easily. Do we consider the paket.target as unchangeable and overwrite it without asking? I'm just asking because users could change it and are not aware of a change.
My proposal is currently supporting ´paket.bootstrapper.exe --self´. I chose that because when we had outages of github it was difficult to even get paket.exe. Should we just show with ´paket outdated´ that the bootstrapper is outdated and show a suggestion.

https://www.nuget.org/packages/Paket.BootStrapper/

Thank you @forki for the package I have included this now.

This issue is still open, because the request of @dnauck for updating the paket.targets file is still unresolved.
I had some time to think about this and thought about that we should maybe let the bootstrapper stick with downloading the latest paket.exe as functionality.
The paket.targets is originally downloaded by the paket.exe when you do paket.exe autorestore on. IMO we should bring the functionality somewhere near here.
My suggestion would be sth like paket autorestore update, to either only update the file or turn the feature off and on. Any other ideas?

Currently the bootstrapper also updates itself via --self on every paket release. Also there is no warning if its outdated, etc.

That would be easily doable. We just display an info when updating that just checks the latest version an displays it.
There is only one problem, that for the github download we cannot detect whether there is a real change @sforki. So each paket release we see immediately an outdated message.

Closing old issue.