On Thu, May 29, 2008 at 2:20 PM, Aaron Griffin <[EMAIL PROTECTED]> wrote: > On Thu, May 29, 2008 at 1:15 PM, Travis Willard <[EMAIL PROTECTED]> wrote: >> On Thu, May 29, 2008 at 2:11 PM, Aaron Griffin <[EMAIL PROTECTED]> wrote: >>> On Thu, May 29, 2008 at 1:02 PM, Jason Chu <[EMAIL PROTECTED]> wrote: >>>> I have a machine that has been put aside for building 64 bit packages. >>>> Now that Aaron's is dead, we could start using this one. I have no >>>> idea how Aaron's was set up so I don't really have an idea on how to >>>> set this one up. >>>> >>>> What is needed for me to make this build machine available? >>> >>> I can do it. Give me sudo access and I will set it all up the same way >>> I had mine setup. >>> >>> It's fairly easy, here are the steps I did: >>> >>> mkarchroot /var/archroot base base-devel sudo >> >> I think it would also be way beneficial to have a testing-enabled >> chroot beside the 'current' chroot. After creating the chroot (say >> /var/archroot-testing), just edit >> /var/archroot-testing/etc/pacman.conf and enable testing, then run >> mkarchroot -u to update the chroot. >> >> Then guys like me can even build against testing packages. Woot. > > Yeah, you'd just have to flip around the ~/chroot-shell/root symlink > to point to different chroots
Or have ~/chroot-shell/ and ~/chroot-shell-testing/ and change where $CHROOT_SHELL points, but yeah
