@pmatilai The project was started in late 2011, like many such things it was a
bit slow to gain traction — between needing plugins or integrated support to be
developed for various editors, and needing to convince users it was worth
bothering with.1 But it's really started to pick up steam in th
> Mock guarantees the "production readiness" and "reproducibility" of the
> result. Running the final -ba without noprep would gain no benefit to mock.
No, it does not. Mock just runs dnf and rpmbuild in repeating sequences. That
doesn't guarantee any reproducibility. What guarantees reproducibi
The sqlite rpmdb as implemented in rpm >= 4.16 by yours truly would probably
get you an F from any self-respecting database course, it's more like a
hole-in-floor toilet train simple thing than a proper database schema. Idea was
to get it working and then move to a fancier schema, but I ran out
Yeah, of course somebody could do just that, and inevitably somebody does
:disappointed:
One possibility may be simply recording the entire rpmbuild cli line into the
built package. That would be more of a generic forensics tool than condemning
--short-circuit but has its own problems wrt repr
