Build multiple PKGBUILDs without cleaning chroot about clean-chroot-manager HOT 3 CLOSED

No time right now but will think about it.

from clean-chroot-manager.

Totally forgot about this request (nearly a year). Please try deb93a3.

from clean-chroot-manager.

Hi graysky. So I started using ccm again yesterday. Found some improvements you could make.

*) You added the 'do not clean chroot before build' option, but if I use that, packages built in the previous execution will not be available in the local repo, because it would not have synced from the root chroot.

*) By default, all build output files and logs are dumped in the PKGBUILD folder. I prefer to keep that folder clean, so I use environment variables to separate them to separate folders. That means the logic for adding built packages to local repo needs to be modified a bit (they are not present in pwd anymore).

One way of fixing the above: https://github.com/siddharthasahu/clean-chroot-manager/commits/features.

Also, I was wondering why you prefer keeping redudant code over using if-else. Keeping only one file for example will make it easier to add features to both 64 and 32 bit versions, no? Just curious how you think about this. :)

from clean-chroot-manager.