[Rpm-maint] [rpm-software-management/rpm] Allow the transaction ID and installation time to be overridden (PR #1803)

[Panu Matilainen]

Do use a per-transaction clock, exactly because a consumer may run multiple independent transactions and if they use a shared clock, the results are no longer independently deterministic (populate transactions A and B, run A, then B vs B then A). Also allows both faked and non-faked transactions in the same process. Neither are the most likely of scenarios but static variables are best avoided, especially when we already have a struct we can easily stick it into and using it seems like the right thing to do anyway.

(I wonder if we could get by with just one tracking variable for this, eg fakeClock == -1 for uninitialized, 0 for disabled and otherwise active. Two variables seems somehow excessive for the case, even though more correct and as if it somehow actually mattered :sweat_smile: )

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1803#issuecomment-950896601
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20211025/4eab82d0/attachment-0001.html>