On Mon, 15 Jan 2024 at 14:54, Jasper Orschulko <[email protected]> wrote: > GitHub also provides tarballs for the unmodified source code, > e.g.:https://github.com/libexpat/libexpat/archive/refs/tags/R_2_5_0.tar.gz > > This corresponds to the "Source Code" asset that Github automatically > adds to releases, see: > https://github.com/libexpat/libexpat/releases/tag/R_2_5_0 > > So if download speeds are a concern, using the source archive tars > would be a valid alternative.
Sadly it wouldn't. Auto-generated github archives are known to be non-deterministic, and we even have a qa check to ensure no recipe is using them. I didn't raise this point because my objections are on the principle of using release tarballs, not this technicality. As for the stuff that autotools-based tarballs add to the pristine git checkout, none of it goes into the target image, and by and large it's the same between all autotools-based projects, so you could probably special-case it into the reports or even the original data. But I would first raise the issue with osselot upstream. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#193677): https://lists.openembedded.org/g/openembedded-core/message/193677 Mute This Topic: https://lists.openembedded.org/mt/103730186/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
