Standardize architecture names within the AppImage community #1299
TheAssassin
started this conversation in
Ideas
Replies: 1 comment 2 replies
-
This is a big mess, not just within AppImage but overall. Everyone seems to have an opinion on this. My 2 cents: "Normal users" with an "Intel" sticker on their computer would not recognize "amd" as something they own. If you ask me, I'd call it "x86-64bit", "x86-32bit", "arm-64bit", "arm-32bit". But I'm not proposing to invent yet-another names. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Given the fact that the architecture names vary a lot on the various distributions, among tools and even within the community, we should invest some effort into standardizing them.
The core of AppImage, namely appimagetool and the runtime, established a scheme already. The following table contains an incomplete listing of different schemes for comparison:
As you can see, AppImage is basically a mix of all of them. I personally like (and prefer) the Debian scheme. But since AppImage already kind of established a scheme, I'd suggest to implement it across the community.
The linuxdeploy projects currently use the AppImage core scheme with a single exception, IA-32 is referred to as
i386
. I will change that soon.We should also document these names in the reference manual on https://docs.appimage.org.
Beta Was this translation helpful? Give feedback.
All reactions