g'day, eh?
in my current employment, i am in charge of a number of YP (well,
Wind River Linux) layers with a lot of legacy cruft^H^H^H^H^H content,
and i'd like to start cleaning it up little by little. i was gifted a
fairly junior co-op student for the term and figured this would be a
good way to put him to use and even turn him into a moderately
competent OE developer by the end of the term.
so i wanted to put together a *really* comprehensive list of best
practices, starting simple, open a Jira epic, and start adding
increasingly sophisticated tasks for him to do day by day.
i've started collecting a few docs but none of them really cover the
gamut of all the pedantic things one could do to tidy up OE/YP layers.
i was going to start off with just aesthetic prettification -- break
absurdly long assignments of multiple values into one per line, line
continuations, in alphabetical order, that sort of thing.
the next step would be, i think, to get familiar with bitbake.conf
and some of the bbclass files, and start removing superfluous content
from various recipes. case in point -- a pile of packagegroup recipe
files unnecessarily set:
PACKAGES = ${PN}
but that's the default so ... delete that sort of thing (as long as
there's no *real* reason for it to be there).
this might sound like grunt work but, as the term went on, i'd ask
him to do more research and come up with cleanups of his own as he
understood more of OE. i'd like to make this a truly productive term
for this guy.
any recommended docs that get to this level? i've already bookmarked
the standard YP docs, and a couple others.
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193541):
https://lists.openembedded.org/g/openembedded-core/message/193541
Mute This Topic: https://lists.openembedded.org/mt/103661346/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
