So to add the repo interaction functionality to the template manager, I've spent a while reading the docs of `python-dnf`. However, it occurred to me that as one should be able to use the manager from both dom0 and mgmtVMs, I have to deal with both `qubes-dom0-update` and `dnf`.
As such, I'm thinking that perhaps invoking the CLI tools -- mostly `dnf
{download,repoquery}`[^1] and the `qubes-dom0-update` equivalents [^2] --
directly might be an easier way of approaching this?
Somewhat related question: is it reasonable to assume that mgmtVMs have network
access? Or do we have to use a mechanism similar to `qubes-dom0-update`
and allow downloading from another updateVM?
[^1]: Interestingly, the output of `dnf repoquery` seems to be
machine-readable.
[^2]: These actions may have to be added.
Thanks,
WillyPillow
> https://blog.nerde.pw/
>
> PGP fingerprint = 6CCF 3FC7 32AC 9D83 D154 217F 1C16 C70E E7C3 1C84
>
> Protonmail PGP = D02D CEFF ACE5 5A7B FF5D 871E 4004 1CB1 F52B 127E
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/dbD900Nz5CHbiMbHVsQboZEjiv8-MTBh4I3h2cY8BZwmxvsyq7FuvIttuyVAD8J5XAaSi980qBEz2tuPWzr7PJDtcIOcv3h-NJvo_lDA7_8%3D%40nerde.pw.
publickey - [email protected] - 0xD02DCEFF.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
