On 13/01/2011 12:54, Nico Kadel-Garcia wrote: > On Thu, Jan 13, 2011 at 7:31 AM, Mister IT Guru<misteritguru at gmx.com> wrote: >> On 13/01/2011 12:26, Nico Kadel-Garcia wrote: >>> On Thu, Jan 13, 2011 at 5:25 AM, Mister IT Guru<misteritguru at gmx.com> wrote: >>>> At the risk of sounding like an newbie, is is possible to build the RPMS >>>> for all architectures on the same box at the same time? I would really >>>> like to automate this, so that I can keep track of the RPMS's and build >>>> them into my own future repo. (That's another project, I'm sure I'll >>>> come to the list for that one!) >>> *IF* your box is an x86_64 box, you can do it. This is usually done >>> with "mock", by using chroot cages with specific layouts and automatic >>> deployment of relevant libraries. >> I have an x86_64 box running Xen, so a paravirtualised guest has just >> been ordered for building a Mock Environment. I'm going to have to run >> to Google to learn more in the short space of time I have open to me, >> you guys seems to be nudging me in the right direction. >> >> Thank you > That is going nto be unnecessarily slow. If you can run mock on the > Xen server itself, you'll get a noticeable speed-up, especially with > large packages like the kernel and Xorg and gimp and Samba. I'm not 100% comfortable with mixing server tasks - especially when the boxes are managed using puppet - (google it, puppet is frikkin awesome!) I always assumed that with paravirtualisation that I'll get near native speeds. Either way, whatever the needs determine - it seems that building a mock environment is the way to go. I'm looking for a mock mailing list, but I guess either this list or the fedora list should be sufficient, right? -- The Solo System Admin - Follow me - I follow you http://solosysad.blogspot.com/ Latest Entry: Bacula - Building from source -- Mister IT Guru At Gmx Dot Com