Wiki gardening for aarch64

[Brendan Conoboy]

Hi everybody,

Adam Williamson mentioned to me that the Fedora wiki was missing an 
entry for Aarch64 on the secondary architecture list.  I've gone ahead 
and updated the architecture page:

https://fedoraproject.org/wiki/Architectures#Secondary_Architectures

To point to the standard ARM page.  By itself this isn't entirely 
satisfactory, since the ARM page itself is still largely 32-bit 
oriented.  Do we want to rework this page for greater aarch64 content or 
do we want to keep this an ARM32 page and add a distinct AArch64 page?

[Marcin Juszkiewicz]

W dniu 18.02.2014 01:15, Brendan Conoboy pisze:
> Hi everybody,
>
> Adam Williamson mentioned to me that the Fedora wiki was missing an
> entry for Aarch64 on the secondary architecture list.  I've gone ahead
> and updated the architecture page:
>
> https://fedoraproject.org/wiki/Architectures#Secondary_Architectures
>
> To point to the standard ARM page.  By itself this isn't entirely
> satisfactory, since the ARM page itself is still largely 32-bit
> oriented.  Do we want to rework this page for greater aarch64 content or
> do we want to keep this an ARM32 page and add a distinct AArch64 page?

I think that as AArch64 is incompatible with ARM we should make separate
page. It is not just rebuild with different flags (like Pidora) but
totally different beast.

[Peter Robinson]

On 18 Feb 2014 00:15, "Brendan Conoboy"  wrote:
> Hi everybody,
>
> Adam Williamson mentioned to me that the Fedora wiki was missing an entry

for Aarch64 on the secondary architecture list.  I've gone ahead and
updated the architecture page:
> https://fedoraproject.org/wiki/Architectures#Secondary_Architectures
>
> To point to the standard ARM page.  By itself this isn't entirely

satisfactory, since the ARM page itself is still largely 32-bit oriented.
 Do we want to rework this page for greater aarch64 content or do we want
to keep this an ARM32 page and add a distinct AArch64 page?
>

Definitely a separate page. We're not intending on doing and form of
multilib between the two so for all intents and purpose its a new
architecture and I'd like to keep it like that to minimise confusion.