| Summary: | Add ability to specify locale base directory | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Paul Eggleton <bluelightning> |
| Component: | core | Assignee: | Unassigned <unassigned> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | meta.mr.watcher, meta.watcher, randy.macleod, sgw, srifenbark |
| Version: | 1.6 | ||
| Target Milestone: | Future | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
I thought this would be straightforward, but it turns out that locale packages get added to the end of PACKAGES, so if your locale files would otherwise be picked up by another package, setting the locale directory to find them won't actually do anything. I'll need to change where these packages are added and that means verifying that doesn't cause any other breakage. There could be some variable descriptions affected for this bug. Minimally, I would think there would be a new variable to define the location of the locale files. I am noting this for when it is fixed. Scott Still a good idea. |
The code in package.bbclass expects to find locales in a fixed directory (${datadir}/locale). This is fine for traditional software packages that use gettext or similar, but not for example for PHP applications that store locale files in a different directory. It would make sense to me to allow the locale base directory to be configured for such recipes.