Arch Linux User Repository

How does this compare to https://github.com/tokland/arch-bootstrap ?

I will check into this... I use ccm all the time on my i7-4790 (9 threads) and see all 8 cores used up. Isn't the default values for MAKEFLAGS 2? Is the bug causing it to use /etc/makepkg.conf on the live filesystem or the default one installed by pacman?

@graysky many thanks for providing this package. I think it had been broken by change in devtools , perhaps this one https://bugs.archlinux.org/task/44827 , which results in makechrootpkg removing MAKEFLAGS set in root/etc/makepkg.conf . The result of this is that THREADS set in ~/.config/clean-chroot-manager.conf is ignored. The working workaround is hinted at in comments to #44827 , which is to create/update ~/.makepkg.conf like this:
MAKEFLAGS='-j17'

I would suggest that, given the availability of a workaround, the proper fix would be to entirely remove THREADS from ~/.config/clean-chroot-manager.conf and scripts, and instead advice user to create/update ~/.makepkg.conf with MAKEFLAGS option.

@graysky: Thanks for your reply. :)

I'm compiling firefox-kde; this package does take a lot of time to build, by tweaking makepkg.conf, adding ccache (although I understand it doesn't work), I hope to improve the build time.

The package I'm using (kmozillahelper) doesn't have Python2/3 as makedeps, so I just installed it manually to the chroot by using the arch-nspawn command.
You are correct this should be corrected in PKGBUILD, but sometimes you may want to install additional packages without having to modify the PKG. :P

CCM doesn't support ccache[1] to the best of my knowledge. You can execute commands within the chroot if you wish and the syntax you proposed is correct. I will consider adding it to the man page. What are you needing to do within the chroot? I'd like to provide an example or 2 but can't really think of anything...

1. https://github.com/graysky2/clean-chroot-manager/issues/23

Hi graysky,

Thanks for providing this chroot manager. :)

Few requests/questions:
- Is it useful to add ccache/--threads=0 inside /chroot/path/etc/makepkg.conf?
- If I understand correctly, commands in the chroot should be execute like so: sudo arch-nspawn /path/to/chroot64/root <command>
If so, could you add it to the readme please. :)

Many thanks!

Thanks for reporting. If you don't have a github account, get one (free) as it makes bug tracking better and doesn't pollute the AUR with bug reports.

That seems to have done the trick!

I see what's wrong. Please try 2.75 which should work in either case.

It works when I use 'ccm <capital es>' to build targetcli-fb-git and the second of the deps (regardless of the order I build the deps). If I don't build the second dep with <capital es> it isn't found when attempting to build t-f-g.

In my case it doesn't make sense to build the second without <capital es>. But in a case where an AUR pkg had one AUR dep, someone might build the dep with <little es> and it wouldn't be found when building the dependent pkg with <capital es>. I confirmed this by modifying the PKGBUILD of t-f-g to only require one of the two, nuked and re-created the chroot, then tried to build t-f-g with <capital es> after building the dep with <little es>. So there's no confusion, it failed because the dep I'd just built couldn't be found:

$ sudo ccm n
$ sudo ccm c
...
$ sudo ccm s
...
==> Making package: python-rtslib-fb-git 2.1.fb59-1
...
$ cd ../targetcli-fb-git
$ sudo ccm S
...
==> Installing missing dependencies...
error: target not found: python-rtslib-fb-git
==> ERROR: 'pacman' failed to install missing dependencies.
...