summaryrefslogtreecommitdiff
path: root/scripts/setup-3rd-party-strata
Commit message (Collapse)AuthorAgeFilesLines
* Dropped support for 'system-kind' from system morphology filesDan Firth2013-09-271-1/+0
|
* Dropped support for 'disk-size' from system morphology files'Dan Firth2013-09-271-1/+0
|
* Fix tests to use rootfs-tarball system-kinds, instead of disksLars Wirzenius2013-04-231-1/+1
|
* Add 'build-mode' field for chunks in a stratumSam Thursfield2013-03-131-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Allowed values: staging: build with a staging chroot (default) test: build with the host's tools bootstrap: build with the host's tools, and do not include this chunk in the final stratum artifact In the past, 'normal mode' has been used to describe building a chunk with the host's tools. We don't want that mode to ever be used, because it is a huge hole in reproducability, but we need to keep it around to avoid making Morph's cmdtest suite depend on Baserock. Hopefully naming it 'test' should discourage potential abusers. It is unfortunate that the build tests now take a separate code path compared to real-world usage of Morph. However, this is necessary to avoid a circular dependency between Morph's test suite and the build-essential stratum in Baserock. We do whole-build testing of Baserock, too, so the 'staging' code path is still tested outside of Morph. However, testing a staging area requires populating it with at minimum a working shell, and this is a bit too complex to go in Morph's test suite.
* tests: Use test: URL prefix instead of baserock: throughoutSam Thursfield2012-11-071-10/+10
| | | | | | | | | | Some tests already used test: and in order to be able to share the scripts/setup-3rd-party-strata script they need to all use the same prefix. Using baserock: implies that we are using real code from Baserock, so I picked test: because the tests only ever use mock morphologies and no real code.
* Split merge tests out from the other branching testsSam Thursfield2012-10-291-0/+136
Merge is by far the most complex of the branching and merging commands.