On Thu, 2023-08-10 at 18:32 +0200, Alexander Kanavin wrote: > On Thu, 10 Aug 2023 at 18:24, Richard Purdie > <[email protected]> wrote: > > I'm thinking having usrmerge disabled makes it more likely we'd notice > > a "bad" tool path creeping into builds rather than the case where the > > host and target share the same paths. That isn't a reproducibility > > case, more a general one. > > But then should we really drop usrmerge/systemd from reproducibility > as the bad path wouldn't be noticed until runtime (or maybe in > package_qa), and that is tested elsewhere?
We do build systemd configurations in multiple places and package_qa checks are run. > FWIW, I'm not particularly happy that systemd is nowadays de facto > dictating filesystem layouts. Or that you can use any libc you like, > as long as it's glibc. And that all/most key developers are employed > by Microsoft. Monocultures are not good, even if source code is > available. I am also a bit worried about that and I don't really want to tie ourselves to that in our test matrix. Whilst removing systemd from there looks fairly drastic, it isn't as bad as it seems. From the reproducibility work, we've now much tighter QA checks in general so the reprodcubility issues appearing now are much reduced and usually toolchain level rather than random path issues which the QA checks now find much earlier. As such, I doubt overall reproducibility will suffer regressions. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#185816): https://lists.openembedded.org/g/openembedded-core/message/185816 Mute This Topic: https://lists.openembedded.org/mt/100663206/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
