Project

General

Profile

Bug #349

master/copy chroots aren't needed since [chcleanup]

fauno - almost 11 years ago - . Updated almost 11 years ago.

Status:
not-a-bug
Priority:
bug
Category:
-
Assignee:
-
% Done:

0%


Description

the idea of having chcleanup was to avoid having to wait for the chroots to synchronize, specially when you're building recursively (with fullpkg or treepkg). since chcleanup is so fast, having a pristine chroot turns out a little overkill. why are both being used on newer libretools?

History

#2

Updated by lukeshu almost 11 years ago

The purpose of having the pristine chroot is now a subset of it's old purpose.

First of all: There are only two cases where it ever synchronizes the chroots:
  1. When you asked for a chroot copy that doesn't exist, it creates one by syncing it
  2. When you manually run `librechroot sync`

Don't think of having the 'root' copy as something to sync to when cleaning, thing of it as a template for new chroots.

If I wanted to build many packages concurrently, I could use `libremakepkg -l $n`, where $n represents that this is the n-th chroot copy. I can adjust how large I let $n get, and it will use the 'root' copy to spin up new copies.

#3

Updated by lukeshu almost 11 years ago

So anyway, the purpose of them is no longer to maintain a "pristine" state, but to serve as a template.

Also available in: Atom PDF