[Slackbuilds-users] using $DOWNLOAD for alt. purpose

[Willy Sudiarto Raharjo]

> So I've got a few scripts that are 64bit only and have different binary 
> files to download for amd64 or aarch64. The scripts are setup to fail on 
> 32bit and I'd like to know if it'd be possible for me to use the 
> $DOWNLOAD for the aarch64 files, so I don't have to omit a otherwise 
> working script for the platform I mostly use.
> 
> As-is this works with the tool "sboui" on my machines and automatically 
> gets the $DOWNLOAD on aarch64 and the correct one on x86_64 as well.
> 
> Would it be acceptable to have the script itself fail on 32bit rather 
> than marking $DOWNLOAD=unsupported so we can offer support for the 
> aarch64 platform?
> 
> Side note: is there any future plans to add a $DOWNLOAD_AARCH64 to the 
> .info?

As far as i can tell, no
Not all admins have access to ARM machines to test the script, so the 
best thing we can do is to offer parameter  flags for ARM architecture.

https://git.slackbuilds.org/templates/commit/?id=20ac57b04874a38a4a1b4aa8d0fa4ec95a5605a4

https://slackbuilds.org/faq/#ports

-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x3F617144D7238786.asc
Type: application/pgp-keys
Size: 8363 bytes
Desc: OpenPGP public key
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230804/3e6bc5b4/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230804/3e6bc5b4/attachment.asc>