OpenEmbeddedJanitors: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
PaulEggleton (talk | contribs) (Remove obsolete item) |
||
Line 1: | Line 1: | ||
Here we have the current "janitor" tasks in OE. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in the system, but which can help acclimate them to contributing to the project. Current tasks: | Here we have the current "janitor" tasks in OE. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in the system, but which can help acclimate them to contributing to the project. Current tasks: | ||
* Make recipes more conform a standard layout (see also contrib/oe-stylize.py, which can be of help here). be careful though if require lines are moved. It is a good plan to test building a recipe after oe-stylizing it and use buildhistory to test for regressions. | * Make recipes more conform a standard layout (see also contrib/oe-stylize.py, which can be of help here). be careful though if require lines are moved. It is a good plan to test building a recipe after oe-stylizing it and use buildhistory to test for regressions. | ||
* Rework files dir. if there is only one recipe in the dir (like x_0.bb and x_1.bb) the dir should be called x, if the patches are only for x_1 then the dir should be called x-1. Also check if the patches in it are still applied or only deadwood. | * Rework files dir. if there is only one recipe in the dir (like x_0.bb and x_1.bb) the dir should be called x, if the patches are only for x_1 then the dir should be called x-1. Also check if the patches in it are still applied or only deadwood. |
Revision as of 16:11, 30 July 2013
Here we have the current "janitor" tasks in OE. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in the system, but which can help acclimate them to contributing to the project. Current tasks:
- Make recipes more conform a standard layout (see also contrib/oe-stylize.py, which can be of help here). be careful though if require lines are moved. It is a good plan to test building a recipe after oe-stylizing it and use buildhistory to test for regressions.
- Rework files dir. if there is only one recipe in the dir (like x_0.bb and x_1.bb) the dir should be called x, if the patches are only for x_1 then the dir should be called x-1. Also check if the patches in it are still applied or only deadwood.