Bug 9980

Summary: create src packages that can be deployed to image targets
Product: [Build System, Metadata & Runtime] OE-Core Reporter: brian avery <brian.avery>
Component: deploymentAssignee: Unassigned <unassigned>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: Low CC: bluelightning, mark.hatle, richard.purdie, sgw
Version: unspecified   
Target Milestone: Future   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description brian avery 2016-07-19 18:06:12 UTC
It would be nice if we could deploy src packages (or a tar archive of downloads used for that image) to an image.  We should also provide the conf dir.  An option to provide some layers (those that aren't on github/oe for instance) would be needed as well.  This would allow people who want to satisfy GPL to have the src collocated with their distro.
Comment 1 Paul Eggleton 2016-07-19 21:06:19 UTC
Possibly related to bug 5437 (though that's specific to RPM).
Comment 2 Richard Purdie 2016-07-21 15:06:32 UTC
This is potentially quite problematic as the source archives can be large (e.g. gcc, kernel, webkit, piglit) and creating a package for each of these will hugely inflate the sstate object size. We'd end up with a copy in do_package sstate and do_package_write_* and would slow down builds quite considerably. We've gone to some lengths to avoid archiving source in the past.

So whilst it may be nice, don't underestimate the huge performance penalty involved and how unpopular this would be.

We do have archiver.bbclass which was designed to allow people to meet license requirements.

I'd also note that there are several styles people want the source in (as a tarball, extracted, patched, unpatched, configured, unconfigured) so even choosing a format for these is hard as every legal department requires something different.
Comment 3 Richard Purdie 2021-09-23 15:36:05 UTC
I doubt we will end up adding this level of source into target packages. We could but it isn't something anyone plans to work on and isn't considered widely useful.