Hi All,
This is really encouraging for all those who are looking forward to see CentOS builds for multiple archs.
+1. Even I would like to support and contribute towards having ppc64 bits of CentOS 7. Looking forward for the session!
Thanks, Srirama Sharma ----------------------------------------------------------------------------------------------------------------------------------------------- Technical Consultant - FSS Industry ISV Enablement Systems & Technology Group | sriramsh@in.ibm.com | +91-80-41777467 (O) +91 9845680980 (M) IBM India Software Labs -----------------------------------------------------------------------------------------------------------------------------------------------
From: Ashish Kumar9/India/IBM@IBMIN To: "The CentOS developers mailing list." centos-devel@centos.org Date: 25/10/2014 12:06 PM Subject: Re: [CentOS-devel] Secondary archs and how we might build them Sent by: centos-devel-bounces@centos.org
Hello KB ,
I am very keen to join this online session and contribute towards porting CentOS-7 build for ppc architecture .
I would thus request for invite to this much awaited hangout session .
Enthusiasts - Please chime in !!!
Thanks and Regards, Ashish Kumar
From: Karanbir Singh mail-lists@karan.org To: centos-devel@centos.org Date: 10/21/2014 10:34 PM Subject: [CentOS-devel] Secondary archs and how we might build them
Sent by: centos-devel-bounces@centos.org
There has been reasonable levels of interest in the various secondary arch's - i386 / powerpc / arm32 / arm64; but the Core SIG team is just too busy to actively participate and deliver on these.
What I'd like to do is run an online session over google hangout + irc, and see if we can get a conversation started on how other people might contribute towards these builds and how we might setup the idea of a secondary architecture that tracks the main x86_64 builds for CentOS-7.
Not sure if there is much interest or value in doing this for the CentOS-5/6 tree's at this point.
I'd like to propose the 31st Oct 2014 as the date to run this, and starting at 10:00 UTC running for 2 hours.
- KB