rouggy
9887b2aa78
'The Evergreen installer will not install either' moves the problem out of OpsLog's reach: the runtime is a Windows component, and on a managed, offline or otherwise locked-down machine it may simply refuse. Microsoft publishes the same runtime in a FIXED VERSION form — a folder an application carries and points at, needing no installation and no administrator. That is exactly this case, so OpsLog now looks for it beside its own executable and uses it when it is there. The versioned subfolder the download unpacks into is handled, because asking someone to flatten it by hand is one more step to get wrong on a machine where nothing starts. No setting for it: that would be a question asked of the one operator least able to answer it. The folder is either there or it is not. The startup log also records the Windows build — the first thing anyone diagnosing a runtime that will not install is going to ask for.
11 lines
273 B
Go
11 lines
273 B
Go
//go:build !windows
|
|
|
|
package main
|
|
|
|
// webView2Version is a Windows question; elsewhere the browser engine comes
|
|
// with the platform.
|
|
func webView2Version() string { return "n/a" }
|
|
|
|
// windowsVersion is a Windows question too.
|
|
func windowsVersion() string { return "n/a" }
|