Thanks for looking at my question.
I mean the seven git apply lines in setup.sh lines 242-249. The last two, for instance, are patches which modify poky by adding patches for bash (for ShellShock).
My question isn't really about what any one patch accomplishes, though. Rather, I'm trying to grok the architecture of the whole image building system (for the Edison in particular). Those bash changes have wound up as patches-in-patches - which seems a peculiar enough way of doing things that I stopped skimming-and-(virtually)-nodding and figured I'd ask how we got here. If nothing else, it seems a mild flaw in the concept of yocto as a system for managing patches that when you've gone to use it you've wound up having to manage patches to manage patches.
For instance, might it make more sense for the content of the tarball to be published as a git repository cloned from (and tracking) the yocto repository but with the additional edison-specific stuff added?
1 of 1 people found this helpful
currently edison only use yocto but unfortunately its not part of (or integrated)
for example you cant find edison in meta-intel
another member already opened a few related questions, for example this one Let's include Edison in the "Official layer for the Intel platform/board support"!