Is there a reason why librewolf.json is one of the only firefox-based browser manifest that didn't adopt the Addition dir approach?
"pre_install": "'LibreWolf-WinUpdater.exe', 'ScheduledTask-Create.ps1', 'ScheduledTask-Remove.ps1' | ForEach-Object { \"$dir/$_\" } | Remove-Item",
"post_install": [
"$Addition = \"$persist_dir\\addition\"",
"if (Test-Path $Addition) {",
" info 'Copying additional items...'",
" Copy-Item -Path $Addition\\* -Destination \"$dir\\LibreWolf\" -Force -Recurse -ErrorAction SilentlyContinue",
"}"
],
"bin": [
[
"LibreWolf-Portable.exe",
"librewolf"
]
],
"shortcuts": [
[
"LibreWolf-Portable.exe",
"LibreWolf"
]
],
"persist": [
"LibreWolf\\distribution",
"Profiles"
],
Is there a reason why librewolf.json is one of the only firefox-based browser manifest that didn't adopt the Addition dir approach?
Extras/bucket/librewolf.json
Lines 13 to 44 in 3c22c27
Most of firefox-based scoop browsers use this:
Extras/bucket/firefox.json
Lines 27 to 50 in bf63d5d
I came up with a mock up, and it should work out of the box: