summaryrefslogtreecommitdiff
path: root/run-bootstrap-in-chroot
Commit message (Collapse)AuthorAgeFilesLines
...
* Make run-bootstrap-in-chroot unless required env vars are setLars Wirzenius2012-02-141-4/+2
| | | | | | | This removes the previous action which tried to be interactive, and let the user continue the build anyway, but since the build will fail in that case, it's better to not let the user continue. Also simplifies things in general.
* Make the parameter to run-bootstrap-in-chroot not be optionalLars Wirzenius2012-02-131-7/+7
| | | | | It is confusing to have a default, especially since it doesn't actually work anymore.
* Always (re-)create the do-squeeze-chroot scriptLars Wirzenius2012-02-131-4/+2
|
* Copy current working directory (= morph repo) into chrootLars Wirzenius2012-02-091-2/+2
| | | | | | The bootstrapping can, for now, only be run from the git repo anyway, so we might as well copy just that into the bootstrap chroot. Everything else will be accessed via git from the git server.
* Copy only the morph repository into the bootstrap chrootLars Wirzenius2012-02-091-1/+2
|
* Make bootstrap build use git bundlesLars Wirzenius2012-02-091-0/+1
| | | | | | Also, run morph update-gits in loop until it succeeds. Gitorious or git or the office network are unreliable enough that otherwise the build pretty much is guaranteed to fail during the initial cloning and fetching.
* Make caller specify $GITS for the location (dir) where git repos areLars Wirzenius2012-02-011-1/+2
| | | | | | The original code was using $HOME, which gets expanded to /root under sudo, and that's not useful. This avoid hardcoding paths into the script.
* run-bootstrap-in-chroot: make a script and run that to chrootRichard Maw2012-01-301-27/+19
| | | | | | | | | | It is often useful to be able to chroot into the system it is easier to investigate build problems there So run-bootstrap-in-chroot will write a script to do this which can then be used to enter the squeeze chroot with ./do-squeeze-chroot bash or enter the baserock chroot with ./do-squeeze-chroot ./do-chroot
* run-bootstrap-in-chroot: Take mirrors from environment variablesRichard Maw2012-01-271-5/+20
|
* run-bootstrap-in-chroot: use backticks instead of $()Richard Maw2012-01-261-1/+1
| | | | vim syntax highlighting thinks that this is not /bin/sh portable
* scripts: use true/false instead of yes/noRichard Maw2012-01-261-8/+8
|
* Actually run pass2Lars Wirzenius2012-01-201-3/+3
| | | | Also, unmount virtual filesystems using the shell function for it.
* Fix snapshotting logic and git repo updatingLars Wirzenius2012-01-201-42/+25
|
* Keep proc, sys mounted only during chroot runsLars Wirzenius2012-01-201-13/+26
|
* Do not put contents of proc, sys in snapshot tarballLars Wirzenius2012-01-201-1/+5
| | | | Do, however, put the actual dirs in the tarball.
* Fix creation of pass1 snapshot tarballLars Wirzenius2012-01-201-1/+1
|
* Fix sh script line continuation indentation bugLars Wirzenius2012-01-201-3/+3
|
* Change snapshot handling to be more flexibleLars Wirzenius2012-01-201-7/+58
| | | | Also, do snapshot of the debootstrapped thing too.
* Improve error recovery and cleanup the chroot dir at startupLars Wirzenius2012-01-191-0/+3
|
* add missing tools to the squeeze chroot so a system image can be builtLars Wirzenius2012-01-191-1/+1
|
* make run-bootstrap-in-chroot build the whole bootstrap, not just pass1Lars Wirzenius2012-01-191-2/+9
|
* Avoid bc as a dependency for baserock-bootstrapLars Wirzenius2012-01-171-1/+1
| | | | | | | | | | We want to avoid having to have bc in the bootstrap environment, since it's yet another thing to install there, and to build in the bootstrap process. bc is only used to compute the number of parallel make jobs. We can approximate the answer easily with expr (but need integer arithmetic so the result is slightly different).
* remove copying of LFS tarballs (it only ever worked for me)Lars Wirzenius2012-01-131-1/+0
|
* add script to run baserock-bootstrap in a newly created clean chrootLars Wirzenius2012-01-131-0/+37