Do we want to deplove for the read screen to make the data reported more useful? I think we need to if we are going to enable sending to a build server at this stage. It would be good to solve to also be able to populate things like estimated image size, warn a user that "stuff" wont fit on a CD... and maybe even predict how large a live image will end up being.
Looks like we do want to depsolve at this stage.
It seems there was a little more logic needed depending on if we are using a kickstart manifest and have customized it or not. Maybe we also need to create a transaction at this point even when using a non-modified manifest.
Working on some magic in the ready_screen.init() screen
Commit 5764871 does the job
Metadata Update from @jsteffan: - Issue assigned to kanarip - Issue set to the milestone: 2.0.3 Release
Log in to comment on this ticket.