Package Details: clean-chroot-manager 2.89-1

Git Clone URL: https://aur.archlinux.org/clean-chroot-manager.git (read-only)
Package Base: clean-chroot-manager
Description: Wrapper scripts for managing clean chroots.
Upstream URL: https://github.com/graysky2/clean-chroot-manager
Licenses: MIT
Conflicts: clean_chroot_manager
Replaces: clean_chroot_manager
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 50
Popularity: 1.363286
First Submitted: 2013-08-18 16:52
Last Updated: 2018-05-29 19:06

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

bronek commented on 2018-05-31 09:52

@ProfessorKaos64 arch-bootstrap will not build any packages. It will perform a part of the installation of a new ArchLinux system in a bootstrap directory (which later would be the root filesystem of the new system). For this purpose, it will download an earlier prepared minimum set of packages, from a given URL. This package clean-chroot-manager can be used to build packages (on an existing ArchLinux system) which will be used for a subsequent installation of a new system, or (most likely) upgrades. You could use these two packages together to create your own fork of ArchLinux if you were really keen

(I know it is almost a year after the question was asked, but perhaps someone will find this answer useful)

ProfessorKaos64 commented on 2017-07-17 16:21

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

graysky commented on 2016-08-23 23:05

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?

bronek commented on 2016-08-23 12:38

@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.

francoism90 commented on 2016-04-03 16:18

@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

graysky commented on 2016-04-03 15:28

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

francoism90 commented on 2016-04-03 15:14

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!

graysky commented on 2016-01-29 20:06

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.

alpha.niner commented on 2016-01-29 17:33

That seems to have done the trick!

graysky commented on 2016-01-29 00:21

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

All comments