All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Chris Larson <clarson@kergoth.com>
Cc: Yocto Project <yocto@yoctoproject.org>,
	"Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Subject: Re: Documentation: Default FILESDIR
Date: Wed, 29 Feb 2012 16:39:52 -0800	[thread overview]
Message-ID: <4F4EC558.3040401@linux.intel.com> (raw)
In-Reply-To: <CABcZAN=xxYE+fxC_VhhsH+53eOMR4EPX4apWOG6Ut7zmOnSqyg@mail.gmail.com>



On 02/29/2012 04:27 PM, Chris Larson wrote:
> On Wed, Feb 29, 2012 at 5:11 PM, Darren Hart <dvhart@linux.intel.com> wrote:
>> When a new user goes to write a recipe and add a patch or other file,
>> they need to understand FILESDIR and where to put these additional
>> files. I scanned the reference manual and the dev manual and came up
>> mostly empty handed. The one glipse of it is in section 5.1.4 of the
>> Reference Manual:
>>
>> "
>> It is useful when making changes directly to the work directory files to
>> do so using the Quilt tool as detailed in the Modifying Package Source
>> Code with Quilt section. Using Quilt, you can copy patches into the
>> recipe directory and use the patches directly through use of the SRC_URI
>> variable.
>> "
>>
>> Unfortunately, this doesn't say where the recipe directory is and what
>> it should be named.
>>
>> Is this documented somewhere that I missed? If not, Scott can you add
>> this task to your list of doc gaps?
> 
> FILESDIR hasn't actually been used (or, shouldn't have been) for
> years. FILESPATH replaced it.

Sorry, I should have said FILESPATH - that's what I get for not looking
it up. The situation is unchanged though.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2012-03-01  0:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01  0:11 Documentation: Default FILESDIR Darren Hart
2012-03-01  0:27 ` Chris Larson
2012-03-01  0:39   ` Darren Hart [this message]
2012-03-01 15:36     ` Rifenbark, Scott M
2012-03-01 15:47       ` Paul Eggleton
2012-03-01 19:17       ` Darren Hart
2012-03-05 11:19         ` Joshua Immanuel

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=4F4EC558.3040401@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=clarson@kergoth.com \
    --cc=inaky.perez-gonzalez@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.