Introduce the _AVAILABLE mechanism
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 of 7 patches 0 repliesNew
3 of 7 patches are in this archive. The cover letter announces 7.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | docs/manual: update 'adding packages' with the new _AVAILABLE symbol | +0 | 1 reply | |
| 1/7 | docs/manual: update 'adding packages' with the new _AVAILABLE symbol | +0 | 1 reply | |
| 2/7 | support/scripts: add a script to add a new package | +0 | 4 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [PATCH 0/7] Introduce the _AVAILABLE mechanism
Quoted 10 lines · Yann E. MORIN
Quoted 4 lines
Quoted 4 lines
There is still an alternative: patch
Kconfigto "properly" handle
select/depend transitivity. I.e., when a symbol selects another symbol, this implies that all dependencies of the other symbol are inherited. Did anyone ever investigate the feasibility of such an feature?Yes. Both Thomas and I have had a look (but separately). I got an headache each time I tried to understand the kconfig code. IIRC, Thomas' experience was a bit in the same vein.
My point of view is that we must consider (unless proven otherwise) that modifying kconfig to handle this select/depends mess is not possible.
I completely agree. But if it had been easy to do, it might have been
preferable over adding verbosity to Config.in.
In that case, I guess I'll have to take the time to review those patches
before Saturday :-)
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286540 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F