Comment # 3 on bug 1017970 from Thomas Renninger

> I think you misunderstand my point.
Hmm, maybe the other way around.

Adding acpica to an already existing aarch64 leap project would certainly need
modifying the package list as well.

A new package showing up in a maintenance update repo is rare, probably needs
leap release manager approval and work. Not worth as this is everything but
critical.

> The people who need it on x86 are the same set of people who will need it on
> aarch64.
No, because people who need acpica typically work on BIOS level, close to HW.
I often debug x86 acpi issues, but fortunately never had the pleasure to look
at aarch64 issues, other than reviewing code.

> > You can build it on your own in our build service.
> Clearly that's not the point
Yes it is. There is an easy way out for the handful aarch64 acpi developers.
Simply clone the original project into your open build service home project and
enable build (and publish flag) for aarch64.
I did that now and it took me 3x longer to write this than to do 2 clicks in
our build service. You can now add this repo:
zypper ar
http://download.opensuse.org/repositories/home:/trenn:/branches:/hardware/openSUSE_Factory_ARM/home:trenn:branches:hardware.repo
if zypper is what you need to work with...

PS: Please read in a bit and try out things mentioned, before answering or
complaining next time.