On 01/28/2013 03:08 PM, Adrian Schröter wrote:
Am Montag, 28. Januar 2013, 14:42:49 schrieb Guillaume Gardet:
Le 28/01/2013 14:36, Adrian Schröter a écrit :
Am Montag, 28. Januar 2013, 13:52:26 schrieb Guillaume Gardet:
Hi,
I think it would be great to have a devel:ARM:AArch64 project (or another name) where we could store all our patches for AArch64. What do you think about it? Yes, but lets not do the mistake to store them there to long. They should get submitted to standard factory as soon as possible (maybe just ensuring that they harm not other architectures :) Ok. What would be the policy? For example, I can build the "rpm" package without selinux support since it is not yet available. Is it ok to add patches to Factory to disable selinux for aarch64? Yes, would be fine. However, for this specific case, disabling core features may turn into a nightmare when one has to adapt lots of packages afterwards ...
But if we want to go that way, better doing it in factory and reverting it also there later. The former ARM ports failed mainly because exactly this merging work was not done.
Then, "autoreconf -fi" fails with an obscure reason. So, I workaround it with "autoreconf -fi || autoconf -fi" for aarch64. I am not sure Factory will accept this kind of workaround. Hm, I would prefer to understand if better ... but in the end, the question is if the individual package owner does accept it or not ;)
I'd be inclined to say that I'd really start worrying about Factory merging as soon as we actually have a base system we can build with :). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org