Re: deduplicating noarch subpackages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le jeudi 13 février 2020 à 09:59 -0800, Josh Stone a écrit :
> 
> It's not so black and white. In theory, the only thing that should
> matter is the target triple, but the metadata also hashes the
> metadata
> of all its build dependencies. That in turn may include procedural
> macros (essentially compiler plugins) which are host binaries. The
> end
> result for the target should be the same, but it's a real concern for
> upstream that ignoring the host would break caching that relies on
> filename differences.

It is so black and white. If you can not produce bit-perfect identical
builds, don’t try to make the result noarch.

Neither koji, nor auditors, nor other third parties, can be expected to
check binary differences for you, and identify what differences matter
and what differences do not matter.

Neither koji, nor auditors, nor other third parties, can be expected to
trust that you did this checking for every single build that differs.

The *only* sane check strategy is a black and white equal/inequal test.

And you can not handwave those concerns aways because you feel your
builds should be noarch (feeling is not implementable in software).

When you write

> it's a real concern for upstream that ignoring the host would break
> caching

you are writing that upstream thinks the result is archful (because if
it actually were noarch, it would be perfectly fine to substitute one
build output for another, and there would be no caching concerns).

The proof is in the pudding. noarch → binary differences do not matter,
they can be removed during the build process, and koji will be happy.
archful → removing differences will break something.

And, removing differences does not necessarily mean removing things.
The reproducible build project didn’t remove timestamps. It just made
sure the same timestamp would be used for all builds.

Regards,

-- 
Nicolas Mailhot
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux