Update name of file that indicates installation version#199
Update name of file that indicates installation version#199jamill merged 1 commit intomicrosoft:masterfrom
Conversation
…sion Update name of file that GVFS installer creates when an on disk version 16 capable installation is first installed.
| @@ -287,28 +287,37 @@ private void CheckEnableGitStatusCacheTokenFile() | |||
| try | |||
| { | |||
| string statusCacheVersionTokenPath = Path.Combine(Paths.GetServiceDataRoot(GVFSConstants.Service.ServiceName), GVFSConstants.GitStatusCache.EnableGitStatusCacheTokenFile); | |||
There was a problem hiding this comment.
I think we should get rid of this file. Comparing the capability file and reboot time should be enough, shouldn't it?
There was a problem hiding this comment.
I see that you discussed this in the PR comments and left it as a TODO. I do think we should drop it, since it's another point of failure and not a necessary one, it would seem.
There was a problem hiding this comment.
@sanoursa I think we should take this PR in isolation for M139 so we can get it out the door.
That would leave us in a state where we could take the second point up in master moving forward, if we felt we needed to revisit it.
There was a problem hiding this comment.
That works for me. The file that is dropped by the installer is one that we will have to maintain forever. The status cache token file is not, so I agree we could clean it up later.
There was a problem hiding this comment.
Thanks! This approach seems reasonable.
|
Scenarios I tested:
|
Update name of file that the GVFS installer creates when an on disk version 16 capable GVFS is first installed.
After discussions on how GVFS determines whether the GitStatusCache should be enabled to ensure that the machine has been rebooted since a GitStatusCache aware GVFS was installed, we decided on two changes:
The name of the file created by the GVFS installer should be changed to
OnDiskVersion16CapableInstallation.datMove the logic for determining whether the GitStatusCache should enabled for a GVFS installation from the GVFS.Service to individual mount processes. This means we could get rid of the
EnableGitStatusCacheToken.datfile that exists in theGVFS.Servicecommon application directory.This PR addresses issue 1.
I want to get agreement on the changes for the file written out by the installer. I can follow up with the changes for the second issue, either for the M139 release, or as a future change.
I am doing another round of testing on these changes, and can do a final verification after we agree on the name.