| Summary: | insane.bbclass: check the /etc/<files> are set by CONFFILES | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Robert Yang <liezhi.yang> |
| Component: | core | Assignee: | Robert Yang <liezhi.yang> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Undecided | CC: | jackie.huang, meta.mr.watcher, meta.watcher, randy.macleod, rongqing.li |
| Version: | 1.9 | ||
| Target Milestone: | 1.9 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Robert Yang
2015-08-06 07:05:51 UTC
As discussed previously, starting here: http://lists.openembedded.org/pipermail/openembedded-core/2014-December/thread.html#100001 and answered here: http://lists.openembedded.org/pipermail/openembedded-core/2014-December/100006.html we can't declare all of /etc/ to be CONFFILES. As Mike Looijmans said: FHS may have written that somewhere, but if you just take a quick look at what is in /etc/, you'll find that actual configuration files are quite rare, but there are tons of scripts and distro related files there. Whether or not a file there is supposed to be edited by the end-user is something of a distro decision. Also, "configuration file" does not necessarily mean that the USER is in control. A configuration file may also simply distinguish machine capabilities or software features. We'll end up having to patch hundreds of recipes with a CONFFILES="" or similar line. So I'm closing the enhancement. If you have a more narrowly specified idea, please open a new enhancement. See previous comment. |