All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: question about "Flexible Inheritance for Class Functions", BB manual
Date: Sun, 21 Mar 2021 03:40:31 -0400 (EDT)	[thread overview]
Message-ID: <60c7c789-acb-d0a0-5cae-f0741fb5b5d@crashcourse.ca> (raw)


  was thinking of tweaking some of this part of the manual, first a
couple questions.

  in that section:

file:///home/rpjday/oe/dist/layers/bitbake/doc/_build/html/bitbake-user-manual/bitbake-user-manual-metadata.html#flexible-inheritance-for-class-functions

the intro correctly explains how one can normally make adjustments to
an inherited task from a class file, i just want to have a complete
list as to the possibilities:

 * do nothing and accept the inherited task as is
 * _append or _prepend (or possibly both) to the task
 * override it completely by redefining the task

i would also have added:

 * delete the task with "deltask"
 * delete the task with var flag "noexec"

first question -- is that pretty much the complete set of what one can
do with regards to an inherited task? am i missing anything obvious?
and the only drawback to providing that list is that deltask and var
flags are explained in subsequent sections so the ordering would be a
bit off.

  also, even if one uses the EXPORT_FUNCTIONS feature, i'm assuming
one can ignore that and still use all of the above unchanged, yes?

  still pondering as to how i'd rewrite this for clarity.

rday

                 reply	other threads:[~2021-03-21  7:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60c7c789-acb-d0a0-5cae-f0741fb5b5d@crashcourse.ca \
    --to=rpjday@crashcourse.ca \
    --cc=docs@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.