All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: kernel manual: confusing coverage of FILESEXTRAPATHS_prepend
Date: Thu, 26 Feb 2015 15:29:01 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.11.1502261526130.5576@localhost> (raw)
In-Reply-To: <3318322.uVudHOlJ9O@peggleto-mobl5.ger.corp.intel.com>

On Thu, 26 Feb 2015, Paul Eggleton wrote:

> Our policy in OE-Core (and the layers under meta-openembedded) is to
> move away from files/ to ${BPN} for a bit of consistency - if you
> use ${BPN} it then doesn't matter if you have more than one recipe
> in a directory, the files for each recipe are still kept separate
> instead of a files/ directory with a mixture of files for different
> recipes. ${BP} would only be used for patches that are specific to a
> version where multiple versioned recipes are being provided, leading
> to multiple versions of the same files needing to be present.

  ok, so ... ${BPN} for single-recipe directories *or* common files
across multi-version recipes, and ${BP} for version-specific stuff?
that's the way i'm reading that. that's good, it's the sort of thing
that would be good in a "style guide."

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:[~2015-02-26 20:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25  8:54 kernel manual: confusing coverage of FILESEXTRAPATHS_prepend Robert P. J. Day
2015-02-25 13:44 ` Joe MacDonald
2015-02-25 13:51   ` Gary Thomas
2015-02-25 15:49   ` Rifenbark, Scott M
2015-02-26  9:12   ` Robert P. J. Day
2015-02-26  9:20     ` Robert P. J. Day
2015-02-26 10:17     ` Paul Eggleton
2015-02-26 20:29       ` Robert P. J. Day [this message]
2015-02-25 17:08 ` Darren Hart

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.1502261526130.5576@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=paul.eggleton@linux.intel.com \
    --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.