[aur-general] package-base PKGBUILD with different architecture list for packages inside
lonewolf at xs4all.nl
Sat Oct 5 14:47:08 UTC 2019
On 05-10-2019 13:48, Attila Greguss via aur-general wrote:
> I have a PKGBUILD Here
> Is there a way to enable the commented out package in the PKGBUILD without
> said package blocking the installation of the other packages on the
> architecture it does not support?
> I'm OK with splitting it out, but I thought I ask first if because I don't
> know the capabilities of PKGBUILD/makepkg.
> Some (not necessary) context:
> Package is for dotnet, and the source archive includes dotnet-host,
> dotnet-runtime, aspnet-runtime, dotnet-sdk for x86_64 and armv7h. For
> aarch64 it does NOT contain aspnet-runtime files, but all the rest.
> I tried to specify the architecture list for aspnet-runtime in the
> PKGBUILD, but if someone tries to install any of the other packages on
> aarch64 it will fail. (see commented out part in file)
Not sure if it will work, but I suggest trying this :
- remove arch=('x86_64' 'armv7h' 'aarch64') from the body
- add the correct arch= inside all package_ functions
In case that doesn't work, this might be a (rather crude) alternative :
- keep arch=('x86_64' 'armv7h' 'aarch64') in body
- in package_aspnet-runtime-2.1
remove arch=('x86_64' 'armv7h')
add statements that
create an empty package when $CARCH='aarch64'
make normal package for 'x86_64' and 'armv7h' arches
More information about the aur-general