Ok, good. For now I think we need to concentrate on the fundamental problem of 
architecture dependency. While most architectures today use 4K pages, being 
common doesn't make it arch independent, and then there are architectures where 
this is configurable (eg aarch64). A noarch package cannot have content that is 
only valid on some architectures.

How are we supposed to deal with this?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1203#issuecomment-636676219
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

Reply via email to