|| ||Bill Nottingham <notting-AT-redhat.com> |
|| ||Development discussions related to Fedora <devel-AT-lists.fedoraproject.org> |
|| ||Re: F20 System Wide Change: ARM as primary Architecture |
|| ||Thu, 11 Jul 2013 13:41:35 -0400|
|| ||Article, Thread
Brendan Conoboy (firstname.lastname@example.org) said:
> I'm not up-to-date on the current condition of Power: Are you
> specifically referring to GNOME & KDE? If so I'd posit that this is
> because GNOME & KDE make a lot more sense on Power than they do on
> ARM. Developer energy goes where it's needed & wanted. Prior to
> this discussion nobody was lamenting the state of gnome on their low
> power ARM system. We're still building them of course- all the
> GNOME and KDE packages are built, they're just not getting used
This seems wildly at odds with
1) what the people using Power in production are targeting (not desktop at
2) what the enthusiast people for ARM are building. After all, the
annoucement explicitly says "The image is available for each of the major
desktop environments" (which, not true), and people in this very thread are
suggesting interested developers get Chromebooks.
I mean, I do know what some people want ARM to be in terms of dense
hypserscale servers (32/64-bit)... but the community that would be using
Fedora ARM does seem to be targeting a wider array than that.
So, in terms of PA, I think there are reasonable guides of parity that need
to be met:
- If a feature claims to be supported on both arches, it should work the same.
Hence, stack-protector needs fixed.
- The main interface for documented Fedora workflows should be the same.
Hence, use of Anaconda, use of systemd, etc.
- The core functionality should work the same
Kernel, glibc, all the core library stacks. And I would argue that yes, this
*includes* libGL. So llvmpipe needs fixed, outside of any desktops. Should
we define the core functionality better? Probably.
- The defaults should be the same.
SELinux on. Filesystem of ext4 (currently), and so forth.
And also therefore, if you're intending to ship/support a desktop use case
(which, from the F19 ARM deliverables seems to be the case), then the same
one that's the default on other primary arches needs to be available, work,
and should be the default on the new primary arch as well.
devel mailing list
to post comments)