Search Criteria
Package Details: clean-chroot-manager 3.04-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/clean-chroot-manager.git (read-only, click to copy) |
|---|---|
| Package Base: | clean-chroot-manager |
| Description: | Wrapper for managing clean chroot builds with local repo therein. |
| Upstream URL: | https://github.com/graysky2/clean-chroot-manager |
| Licenses: | MIT |
| Submitter: | graysky |
| Maintainer: | graysky |
| Last Packager: | graysky |
| Votes: | 70 |
| Popularity: | 1.15 |
| First Submitted: | 2013-08-18 16:52 (UTC) |
| Last Updated: | 2026-04-18 16:22 (UTC) |
Dependencies (5)
- bc (bc-ghAUR)
- devtools (devtools-gitAUR, devtools-doasAUR)
- libarchive (libarchive-gitAUR)
- pacman (pacman-gitAUR, pacman-fancy-gitAUR)
- rsync (rsync-gitAUR, rsync-reflinkAUR)
Latest Comments
1 2 3 4 5 6 .. 10 Next › Last »
graysky commented on 2026-04-12 15:07 (UTC)
Version 3.0 introduces optional multiple simultaneous building. It's relatively new, but it seems to be working fine in my test cases. If you discover any bug, please open an issue on GitHub.
jfk9w commented on 2025-01-18 14:24 (UTC)
bc should be added to dependencies
/usr/bin/ccm: line 357: bc: command not foundLone_Wolf commented on 2024-03-09 12:57 (UTC)
I had some issues and decided to give ccm another try.
It's working fine now using my own pacman & makepkg settings, including the ccache data sharing. I especially like that you have put the chroot_local repo above all others.
That has saved me some headaches were I had to add packages manually to prevent pacman from using repo packages when using devtools..
graysky commented on 2019-10-23 22:28 (UTC)
All - I added support for an external makepkg.conf and pacman.conf in 2.201-1 ... lots of internals changed so please test and use the github page to report any issues.
graysky commented on 2019-10-23 17:42 (UTC)
@artafinde - Yes, ETA 9 min ago :p
artafinde commented on 2019-10-23 08:21 (UTC)
@graysky any ETA on pacman >= 5.2 support? This already hit stable repos today.
graysky commented on 2019-10-16 18:25 (UTC)
I replied to the closed ticket, https://github.com/graysky2/clean-chroot-manager/issues/57
gillecaluim commented on 2019-10-16 18:13 (UTC)
t really doesn’t matter what packages I’m building I have to nuke and create after the first package which completely defeats the purpose of ccm for me
jpapadopoulos commented on 2019-10-16 08:36 (UTC) (edited on 2019-10-16 08:46 (UTC) by jpapadopoulos)
Hi, I'm also getting that error(Failed to stat /repo: No such file or directory) after building llvm-minimal-git and then trying to build mesa-git with "ccm64 S". This happened with a freshly nuked chroot. Trying to use "ccm64 s" for mesa-git instead gives me the following error "Failed to resolve /home/user/Data/chroot/user//home/user/Data/chroot//root/repo: No such file or directory"
https://github.com/graysky2/clean-chroot-manager/issues/57
1 2 3 4 5 6 .. 10 Next › Last »