[Slackbuilds-users] About aarch64 support support in TEMPLATE.info

[Willy Sudiarto Raharjo]

> Hello, this is just an information post if you want to discuss-test it.
> Personally I dont have aarch64 but almost in every of my
> package-bin.SlackBuilds there are
> available packages for arm64(aarch64).
> Also most projects can be compiled in aarch64 nowadays.
> For now there is no option in TEMPLATE.info to support arm64.tarball
> for download.
> A solution to add them in info file like this:
> 
> DOWNLOAD_x86_64="url/amd64.deb \
>   url/arm64.deb"
> MD5SUM_x86_64="efgh5678_amd64 \
> 1234abcd_arm64"
> 
> works because SlackBuild script picks the correct tarball for compile
> or repackage but we still have to download both files locally.
> 
> I did tried an TEMPLATE.info like this:
> https://github.com/rizitis/sbopkg_hacks/blob/aarch64/template.info
> 
> and worked fine with 2 package managers I test (sbopkg,slpkg) in my
> x86_64 system, didnt tried sbotools* so far but I dont think it will
> have problems also.
> 
> I mean if we don't create conflicts for package managers then it wont
> be so hard to appears in SlackBuilds.org Web page
> Source Downloads:
> link/tarbal-i?86
> link/tarbal.x86_64
> link/tarbal.arm64
> 
> For sbopkg specific I made a fork with a small patch and it seems to
> work and support this TEMPLATE.info
> https://github.com/rizitis/sbopkg_hacks/tree/aarch64
> 
> I m sure that for sbotools*, slpkg etc... maintainers will  easy fix
> what needed in future (if you adopt this TEMPLATE.info future)
> 
> What will probably be hard sbobot, that is something I have no idea
> how easy will be or if arm64 tarball will stay as UNTESTED as this is
> already happening now.
> For me that will be fair enough, but that's me...
> 
> Any way this email is just some test i did and one idea for the
> future, nothing more.
> Thats why i didnt even made PR in sbopkg master branch for my patch.
> I have the idea and my knowledge stop here.
> The rest (if any) are for more experts!

This is my *personal* opinion, so other admins might have different idea

1. This is not the official Slackware project although it shares most of 
the basic scripts.
2. Not all of the admins/maintainers have or plans to use this 
architecture on their machines.
3. More burden for maintainers and admins if this is added into the 
template since they need to test more
4. We don't have the CI support as of now for AARCH64, only relies to 
the current maintainer that they test it.
5. Changes needed in our backend infrastructure (website, database, etc) 
and so far no one is interested to take this work.

So i'm not really sure if this is going to work (at least for now until 
most of those points are resolved).


-- 
Willy Sudiarto Raharjo
-------------- 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/20250416/81558345/attachment.asc>