88ffdc0ae2
This currently requires a `--i-know-this-is-experimental` flag; I know it'd be a bit more consistent to have it under `ex`, but what feels weird about that is *most* of the `ex` commands people use are client side. This is where we want it to ultimately end up. We've landed a lot of prep patches, but I know there's still a notable amount of code duplication with `compose tree`. What's left is about ~700 lines but it's mostly not hard/complex code anymore. In the future, I'd like to extract more of the compose code to a `rust/src/compose.rs` or so, but I think this is sustainable fow now. My high level goal is to get this into coreos-assembler and stand up a Silverblue build that uses it. Closes: #1512 Approved by: jlebon
34 lines
879 B
Bash
Executable File
34 lines
879 B
Bash
Executable File
#!/bin/bash
|
|
|
|
set -xeuo pipefail
|
|
|
|
dn=$(cd $(dirname $0) && pwd)
|
|
. ${dn}/libcomposetest.sh
|
|
. ${dn}/../common/libtest.sh
|
|
|
|
prepare_compose_test "rojig-pure"
|
|
pysetjsonmember "automatic_version_prefix" '"42"'
|
|
mkdir cache
|
|
mkdir rojig-repo
|
|
runcompose() {
|
|
(cd rojig-repo && createrepo_c .) && \
|
|
rm -f treecompose.json && \
|
|
rpm-ostree compose rojig --write-composejson-to $(pwd)/treecompose.json --cachedir=$(pwd)/cache ${treefile} $(pwd)/rojig-repo "$@" && \
|
|
(cd rojig-repo && createrepo_c .)
|
|
}
|
|
|
|
runcompose
|
|
test -f treecompose.json
|
|
test -f rojig-repo/x86_64/fedora-atomic-host-42-1.fc28.x86_64.rpm
|
|
echo "ok rojig ♲📦 initial"
|
|
|
|
runcompose
|
|
test '!' -f treecompose.json
|
|
echo "ok rojig no changes"
|
|
|
|
pysetjsonmember "documentation" 'False'
|
|
runcompose
|
|
test -f treecompose.json
|
|
test -f rojig-repo/x86_64/fedora-atomic-host-42.1-1.fc28.x86_64.rpm
|
|
echo "ok rojig dropped docs"
|