[OE-core] wanting to clarify patch mechanics

Robert P. J. Day rpjday at crashcourse.ca
Sat Jul 7 10:04:07 UTC 2012


  not sure if there's a more comprehensive coverage of how OE patches
work than the brief discussion in the bitbake user manual, but i'd
like to clarify the variations just so i can document them.

  here's what's in the bitbake manual that seems to be the entire
coverage of patches:

SRC_URI= "file://relativefile.patch"
SRC_URI= "file://relativefile.patch;this=ignored"
SRC_URI= "file:///Users/ich/very_important_software"

and so, to questions.

  first, what is this "this=ignored"?  does that still exist?  is it
equivalent to "apply=no"?  i don't see a single example of
"this=ignored" anywhere throughout oe-core, but i see a single example
of "apply=no" in net-tools_1.60-23.bb.

  speaking of apply, it would seem that "apply=yes" is redundant, is
that correct?  there are a couple dozen examples of that throughout
oe-core, mostly in the bash recipe file.  is there anything subtle
about that parameter, or is it truly superfluous?

  there's no mention of the "striplevel" parameter in the manual,
which i think would be useful, and that its default value is "1".  and
i can see the warning that "pnum" is deprecated in favour of
"striplevel", but at the moment, i see not a single usage of "pnum"
and wonder if that warning can just be tossed and support for "pnum"
abandoned entirely.  (there's not a single usage of "pnum" anywhere in
the entire yocto pull, either.  just an observation.)


  i think that's all i had for now.  anything else about patches worth
writing down?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================




More information about the Openembedded-core mailing list