Le mercredi 01 mai 2019 à 13:12 +0100, Tomasz Kłoczko a écrit : > On Wed, 1 May 2019 at 09:04, Nicolas Mailhot < > nicolas.mailhot@xxxxxxxxxxx> wrote: > [..] > > > One of those specs is elfutils.spec in which is: > > > > > > %check > > > # Record some build root versions in build.log > > > uname -r; rpm -q glibc > > > > Funny; that’s pretty much > > https://github.com/rpm-software-management/rpm/issues/607 > > > > that upstream does not want to acknowledge. > > IMO maintainer in this case is 100% right because all properties of > the build env already can be described in with enough precision. > Providing more details about build env will be duplicating current > build dependencies. You're confusing constrains (build dependencies) with actual build env composition (exact constrains resolution, which has been known to change even with the same package set, just by switching dependency resolution engines from yum to dnf to whatever). Build env composition information is generally useful for audits, reproducibility, and debugging. It's useful enough to have been reimplemented over the years in multiple places (elfutils spec, koji, whatever). It's even more useful with the recent tendency to static build. What is missing is a mecanism to record in in a generic way package- side, so one does not have to rely on build farm logs (that may or may not be retained over time) to access this basic info. Computing this info is trivial. It’s just a rpm -qa at the end of buildrequires resolution. Accessing this info reliably, however, it not trivial today, because the storage part has not been streamlined. -- Nicolas Mailhot _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
