[arch-dev-public] Punishment needed for not building in a chroot
thayerw at gmail.com
Wed Dec 23 13:58:54 EST 2009
On Dec 23, 2009 at 10:48 AM, Thayer Williams <thayerw at gmail.com> wrote:
> On Dec 06, 2009 at 05:58 PM, Allan McRae <allan at archlinux.org> wrote:
> > Paul Mattal wrote:
> > >Then I need to find the pacman.conf and makepkg.conf.
> > That is optional. But most people want to keep their makepkg.conf
> > for the PACKAGER variable and MAKEFLAGS.
> What happens if we don't provide the -C and -M flags when building the
> chroot? Are default configs provided? The wiki seems to suggest that by not
> providing these flags mkarchroot will instead use 'dirty' configs.
> The first time through the steps I grabbed the vanilla makepkg.conf and
> pacman.conf from the pacman source, thinking that's what the wiki meant. Of
> course that didn't work because makepkg.conf contains @ARCH@ instead of the
> actual architecture.
> I'm probably the only idiot who's done this, but ambiguity remains for those
> with no experience in this stuff.
Ignore this question, I just saw the subsequent post from Paul. I think the
whole -C -M bit should be removed from the article, or at least listed as a
separate (alternative) command. I'll update the wiki at some point today.
More information about the arch-dev-public