[Feature] add `archvar` in `architecture` and use it in `env_add_path`, `bin`, `shortcuts` etc rather than stuffing these hard-coded inside `architecture`

[goyalyashpal]

Summaries & Titles

• add something like archvar in architecture and use it in env_add_path, bin, shortcuts etc rather than stuffing these hard-coded inside architecture

Feature Request

Is your feature request related to a problem? Please describe.

• for packages which have arch dependent env_path, bin, or shortcuts;
• the current approach is to put these repeatedly in the each of architecture.<arch>
• otherwise, problems shared by @ issaclin32 in reply to @ rashil2000 at ScoopInstaller/Main#2784 come up
• https://github.com/ScoopInstaller/Scoop/issues/1372#issuecomment-419249742

i.e. you want to:

• be able to select or deselect an arch (like with nesting currently)
• while simultaneously getting DRYness & leanness of global vars

Describe the solution you'd like

the basic idea is to define a variable (say archvar) in each arch of architecture i.e. at architecture.<arch>.archvar, then using that in the global definition of all these other fields.

fields like:

• bin, shortcuts
• env_add_path, env_set
• maybe even autoupdate..url & autoupdate..regex too lol but i can't fathom that right now, so, it isn't enacted in examples. also, this will likely intermingle the manifest-update logic with manifest-install logic which would be unwanted

more details posted at this comment below: https://github.com/ScoopInstaller/Scoop/issues/5961#issuecomment-2106383595

example manifest

examples posted at this comment below: https://github.com/ScoopInstaller/Scoop/issues/5961#issuecomment-2106380121

Describe alternatives you've considered

[goyalyashpal]

Example manifests

• this section inspired from: https://github.com/ScoopInstaller/Scoop/pull/3518 & comments

found using github.com/search on searching by nesting's 8-space indent for:

• nested bin
• nested shortcuts
• nested env_add_path
• nested env_set

main/autoit: "_x64", ""

https://github.com/ScoopInstaller/Main/blob/7303e0576ff3f4a616f9796941974615a616e0c6/bucket/autoit.json#L33 ```json { "version": "3.3.16.1", "description": "Scripting language designed for automating the Windows GUI and general scripting", "homepage": "https://www.autoitscript.com/site/autoit/", "license": { "identifier": "Freeware", "url": "https://www.autoitscript.com/autoit3/docs/license.htm" }, "suggest": { "vcredist": [ "extras/vcredist2005", "extras/vcredist2008", "extras/vcredist2022" ], "AutoIt Script Editor": "extras/autoit-script-editor" }, "url": "https://www.autoitscript.com/files/autoit3/autoit-v3.zip", "hash": "8b7098c44275d0203c23f2ce56c0e913c0d6b6d2264bc537e8a9f0a9f07badc9", "extract_dir": "install", "architecture": { "64bit": { "archvar": "_x64" }, "32bit": { "archvar": "" }, }, "bin": [ [ "AutoIt3$archvar.exe", "AutoIt" ], [ "Aut2Exe\\Aut2exe$archvar.exe", "Aut2exe" ], "Au3Check.exe" ], "shortcuts": [ [ "AutoIt3$archvar.exe", "AutoIt" ], [ "Au3Info$archvar.exe", "AutoIt Window Info Tool" ], [ "Aut2Exe\\Aut2exe$archvar.exe", "AutoIt Script Compiler" ], [ "SciTe\\SciTE.exe", "AutoIt Script Editor" ] ], "post_install": [ "$editor = versiondir 'autoit-script-editor' 'current'", "if (Test-Path $editor) {", " Remove-Item \"$dir\\SciTe\" -Recurse -Force", " New-Item -Path \"$dir\\SciTE\" -Value \"$editor\" -ItemType Junction | Out-Null", "}" ], "checkver": { "url": "https://www.autoitscript.com/site/autoit/downloads/", "regex": "v([\\d.]+)" }, "autoupdate": { "url": "https://www.autoitscript.com/files/autoit3/autoit-v3.zip" } } ```

main/miktex: "x64"

https://github.com/ScoopInstaller/Main/blob/5354865fb1477c403de1999bfbea481e2190a786/bucket/miktex.json#L9 ```json { "version": "24.1", "description": "MikTeX, an up-to-date implementation of TeX/LaTeX and related programs.", "homepage": "https://miktex.org", "license": { "identifier": "LPPL1.3c,GPL-3.0-or-later,Public Domain,...", "url": "https://miktex.org/copying" }, "architecture": { "64bit": { "url": "https://mirrors.mit.edu/CTAN/systems/win32/miktex/setup/windows-x64/basic-miktex-24.1-x64.exe", "hash": "94ddd75e2b90309b75db6dbda7d8103fcebda4495b579695e925e885d2b92704", "archvar": "x64" } }, "bin": [ [ "texmfs\\install\\miktex\\bin\\$archvar\\miktex-console.exe", "miktex", "--hide --mkmaps" ] ], "shortcuts": [ [ "texmfs\\install\\miktex\\bin\\$archvar\\miktex-console.exe", "MiKTeX Console" ] ], "env_add_path": "texmfs\\install\\miktex\\bin\\$archvar", "installer": { "args": [ "--portable=$dir", "--unattended", "--private" ] }, "persist": "texmfs\\config", "checkver": { "url": "https://miktex.org/download", "regex": "basic-miktex-([\\d.]+)-x64\\.exe" }, "autoupdate": { "architecture": { "64bit": { "url": "https://mirrors.mit.edu/CTAN/systems/win32/miktex/setup/windows-x64/basic-miktex-$version-x64.exe" } }, "hash": { "url": "https://miktex.org/download", "regex": "(?sm)$basename

[goyalyashpal]

Describe the solution you'd like

• being able to specify some variable inside the each of the architecture, say archvar or archspec or archdir or (as used by context typesetting:) platform
• and then using that in the (global) bin, shortcuts, env_add_path, env_set etc
• this way, the manifests will become much more DRY, leaner & easier to follow

a nuance:

• set it to "" (empty string) to indicate empty string, but valid
• set it to null to indicate invalid ~but i think this would be superfluous - as in, why is that arch there in first place if it's invalid~
• this invalid case can be used at place where some arch doesn't fit this generalisation say, bin doesn't exist for 32bit or there's inconsistency in archvar for some of the variables for an \

but what would be its default value? i.e. what will happen in following cases:

• where it's used in global definitions (say bin) & is not defined in at least one of the otherwise used archs? i'd say that such a manifest itself should be discarded right at the schema level.