| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
This makes modifications and updates of base_chroot easier.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We no longer bind /etc/portage to WORK_CHROOT. Instead we copy it first to
BASE_CHROOT where user can modify settings without touching machine
settings
Also DISTDIR/PKGDIR can be modified in make.conf and we will map these
directories inside chroot instead of standard paths (note that this is
quite possibly buggy, especially make.conf parsing). If these dirs don't
exist outside of chroot they will be created so watch out!
All of this is supposed to take care of various RO mounts over nfs
|
| |
|
|
|
|
|
| |
This should make it more foolproof in case some files are still in use
when unmounting
|
|
|
|
| |
forgot to change WORK_CHROOT to BASE_CHROOT..
|
|
|
|
| |
namely /etc/resolv.conf and make.conf
|
| |
|
|
|
|
|
| |
especially /usr/portage is remounted read only inside chroot instead of
copying it around (silly idea from the beginning)
|
|
|
|
| |
so that we don't fry our own accidentaly /dev
|
|
|
|
|
| |
By deleting BASE_CHROOT.tar and modifying BASE_CHROOT we can modify
further WORK_CHROOTs created
|
|
|
|
|
|
|
|
|
| |
Usage:
For first run stage tarball has to be specified (also portage_dir if it's
not /usr/portage). For subsequent executions only base_chroot (created
during first run and optionally modified) and work_chroot need to be
supplied
|
| |
|
| |
|
|
|