| Summary: | create src packages that can be deployed to image targets | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | brian avery <brian.avery> |
| Component: | deployment | Assignee: | 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
Possibly related to bug 5437 (though that's specific to RPM). 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. 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. |