Changing the paket tool path

I'm using paket within a monorepo with potentially many applications in it. For portability I want to commit a paket.exe bootstrapper tool to the repo, but for space/performance reasons I'd really rather only commit one of these binary files rather than one for each app. Ideally I would commit it to ./.paket/paket.exe at the root and each app within it would know to use the tool up there for restore commands rather than look for it in the .paket folder in the app's own root, where its dependencies and lock files are.

This works ok by changing the Paket.Restore.targets' PaketToolsPath property to the out-of-convention path, except that every time a paket command is run it attempts to revert the file back to its default. At some point a dev is bound to run a build, accidentally commit the re-generated file, and break the build for everyone else. Also it's a bit annoying to keep undoing the overwrite instead.

Is it possible there could be an option added to not overwrite Paket.Restore.targets on paket commands if it already exists, eg. in paket.dependencies or better in Paket.Restore.targets itself? At the moment using paket in a monorepo (not my choice) means committing many (admittedly, relatively small) binary files which bloats the repo and feels a bit unnecessary.

Start by inspecting Paket.Restore.targets and the paket command behavior that regenerates it, along with the possible configuration location in paket.dependencies. Done means a monorepo can use a shared ./.paket/paket.exe without commands overwriting an existing custom PaketToolsPath configuration.