All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: more BSP Guide pedantry involving customizing a recipe
Date: Tue, 30 Dec 2014 14:31:34 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.11.1412301427370.12620@localhost> (raw)


  (you can tell i'm bored and want to get back up to speed on stuff
...)

  section 1.4 in BSP Guide, "Customizing a Recipe for a BSP", appears
to discuss a new layer, "meta-xyz", then suggests the new "interfaces"
file for this machine needs to go at the location:

meta-xyz/recipes-core/init-ifupdown/files/xyz/interfaces
                                          ^^^ ???

  but the files/ subdirectory of "xyz/" would appear to be necessary
(as we all know) only if this was a more general layer that
represented several machines (say, meta-ti) for which we *needed* to
distinguish between machines.

  so while the above might be technically correct, it might mislead
readers to think they *needed* to create a "xyz/" subdirectory for
that overriding interfaces file.

rday

-- 

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

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


             reply	other threads:[~2014-12-30 19:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30 19:31 Robert P. J. Day [this message]
2014-12-30 22:48 ` more BSP Guide pedantry involving customizing a recipe Gary Thomas
2014-12-30 23:37   ` Gary Thomas
2014-12-31 10:06   ` Robert P. J. Day
2015-01-05 23:42 ` Rifenbark, Scott M

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=alpine.LFD.2.11.1412301427370.12620@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=yocto@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.