summaryrefslogtreecommitdiffstats
path: root/packaging/win/build-win-msix.ps1
diff options
context:
space:
mode:
Diffstat (limited to 'packaging/win/build-win-msix.ps1')
-rw-r--r--packaging/win/build-win-msix.ps110
1 files changed, 4 insertions, 6 deletions
diff --git a/packaging/win/build-win-msix.ps1 b/packaging/win/build-win-msix.ps1
index 9f7f667..2aeb2b8 100644
--- a/packaging/win/build-win-msix.ps1
+++ b/packaging/win/build-win-msix.ps1
@@ -4,15 +4,14 @@
+ ffmpeg), packaged for Microsoft Store submission instead of NSIS.
.DESCRIPTION
- See C:\Users\admin\devel\msix-installer.md for the plan this implements.
Unlike Light, this target does NOT drop anything from Full's feature
set -- it exists because Store certification of the NSIS "MSI/EXE"
submission failed for a reason MSIX sidesteps entirely (an unsigned,
internet-downloaded installer never gets a chance to run under
- Microsoft's own unattended validation bot; see msix-installer.md §2),
- not because the bundled node/service-mode/autostart machinery needed
- removing. The one real change is *when* the two elevated operations
- (firewall rule, service-mode install) can happen: an AppX/MSIX install
+ Microsoft's own unattended validation bot), not because the bundled
+ node/service-mode/autostart machinery needed removing. The one real
+ change is *when* the two elevated operations (firewall rule,
+ service-mode install) can happen: an AppX/MSIX install
never elevates, so neither can run at install time the way
build/installer.nsh's customInstall macro does. Both already have an
elevation path that does not depend on the installer at all --
@@ -126,7 +125,6 @@ if ($pkg) {
Write-Host "OK package: $($pkg.FullName)" -ForegroundColor Green
Write-Host (" ({0:N0} MB)" -f ($pkg.Length / 1MB))
Write-Host " unsigned by design -- Microsoft signs it at publish time" -ForegroundColor DarkGray
- Write-Host " (msix-installer.md 3)." -ForegroundColor DarkGray
}
else {
Write-Host "!! no *.appx found in $Client\dist-msix" -ForegroundColor Red