core/sdk: fix relative symlinks in generated tarball (branch yem/sdk)
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 2 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [PATCH 0/2] core/sdk: fix relative symlinks in generated tarball (branch yem/sdk)
Quoted 8 lines · Joel Carlson
Quoted 7 lines · Yann E. MORIN
An other approach, would be that we whietelist certain PATHs from our SDK. Afterall, there are things we do not care about in the SDK. For example, most executables in staging/{,usr/}{,s}bin are not needed. We only really need libs and headers, so we could just ignore anything that is not in staging/{lib,usr/lib,usr/include}/
With per-package staging, could this be done before the per-package staging areas are combined? The idea would be to reduce differences between the stage in buildroot and the stage when using an SDK. Every difference is a possible source of problems, even if it is something that we are not supposed to care about.
Could this be taken further, and everything not in the stage whitelist be deleted? It would be nice if the SDK were smaller.