Because right now qvm-template is fundamentally a cli tool that has its logic interspersed with output, it means as opposed to most other VM and template related functionality there's no library to use that would give access to progress information or even just the ability to install anything in the first place.
This would best be solved upstream by breaking apart functionality and UI in qvm-template, however that's probably a bigger task then umami development itself, so maybe parsing cli output is the way to go at least temporarily.
[Context](https://codeberg.org/eaon/umami/src/commit/1230d30ad2a542426cdb2ebdef2bbc8f9653a603/umami/__init__.py#L324-L326)
Because right now [`qvm-template` is fundamentally a cli tool](https://github.com/QubesOS/qubes-core-admin-client/blob/main/qubesadmin/tools/qvm_template.py) that has its logic interspersed with output, it means as opposed to most other VM and template related functionality there's no library to use that would give access to progress information or even just the ability to install anything in the first place.
This would best be solved upstream by breaking apart functionality and UI in `qvm-template`, however that's probably a bigger task then `umami` development itself, so maybe parsing cli output is the way to go at least temporarily.