Suppose you are working on multiple fixes meaning you are installing multiple packages for different purpose all this done over a weekend. So if you use standard dnf to handle that it will do cleanup in chronological order not to mention the time spend on untangling packages from memory to identify where you used it. This is where Labeled shines!
Labeled treats installations as isolated, logical tags rather than a single linear timeline. You can tear down session A while keeping sessions B and C completely intact, regardless of the order they were installed.
>A few hours later:
>You don't remember what you installed.
There's no such issue with dnf, it has `dnf history` which, well, does what your utility do.
See what you've installed with `dnf history info ...`, undo with `dnf history undo ...`.
Suppose you are working on multiple fixes meaning you are installing multiple packages for different purpose all this done over a weekend. So if you use standard dnf to handle that it will do cleanup in chronological order not to mention the time spend on untangling packages from memory to identify where you used it. This is where Labeled shines!
Labeled treats installations as isolated, logical tags rather than a single linear timeline. You can tear down session A while keeping sessions B and C completely intact, regardless of the order they were installed.
Oh, for a several sessions? Yes, this sounds useful.
I usually just switch to systemd-nspawn --ephemeral containers derived from my host rootfs for such cases, not to pollute the rootfs at all.