@dmnks converted this issue into discussion #2767.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/622#event-10965344679
You are receiving this because you are subscribed to this thread.
Message ID:
This needs an rpmte/rpmts API rework to be sane, currently its ridiculously
cumbersome to find the element you just added in order to add some extra data
to the element. There are several use-cases that would benefit from such work
though.
--
You are receiving this because you are subscribed
Commit b3fcaba3816aa00f3360efe728dafa72e394f65b added a tag reservation
basically just for this purpose but the implementation got stalled with various
underlying defiences, side-issues and API considerations.
--
You are receiving this because you are subscribed to this thread.
Reply to this
The idea has been bandied about before to migrate the "reason" info stored in
yumdb (now using SWDB in newer versions of DNF). I don't know what really holds
up a potential implementation of this in the rpmdb.
@dmach, @ffesti, @pmatilai: what do you guys think?
--
You are receiving this
When installing anything on the system all packages are treated as equals,
which in turn makes it pretty hard to interpret wether user decided to install
package A or if it was pulled and installed only as dependency.
It would be nice to store a marker for each package to figure out where it
