53df522f2b8a989d756cc71ccc430935312b43ff
A new script compose-create-next-dir is added, it can create empty directory for next compose, compose ID is determined by parsing the config file.
get_compose_dir is copied from pungi with minor changes. Pungi is not intended to be used as a library, so not import pungi to use the function.
Signed-off-by: Qixiang Wan qwan@redhat.com
Is this condition always going to evaluate to True? (I understand the code is coming from Pungi which has this useless condition as well, but why not improve it.)
True
rebased
good catch, updated, I'll update pungi as well.
Looks good to me, merging.
Pull-Request has been merged by lsedlar
What's the purpose of this? You really can not know the next compose id until you run it.
@ausil The ultimate goal is better automation of composing. The point is to start the compose in that particular directory and have the path (and compose id) available without parsing the output (essentially moving the starting of compose to another tool). This is not yet going the whole way yet.
A new script compose-create-next-dir is added, it can create empty
directory for next compose, compose ID is determined by parsing the
config file.
get_compose_dir is copied from pungi with minor changes. Pungi is not
intended to be used as a library, so not import pungi to use the
function.
Signed-off-by: Qixiang Wan qwan@redhat.com