From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: yocto@yoctoproject.org
Subject: Re: How to customize a file coming from another recipe?
Date: Thu, 10 Oct 2013 11:33:12 +0100 [thread overview]
Message-ID: <3776909.Wq363vMS5E@helios> (raw)
In-Reply-To: <CAP71Wjz=2tpUFK=CeOWQshm4z91Yu5r-_xGUo+CeuWVaU3NcPg@mail.gmail.com>
On Thursday 12 September 2013 13:53:49 Nicolas Dechesne wrote:
> On Thu, Sep 12, 2013 at 12:16 PM, Paul Eggleton <
> paul.eggleton@linux.intel.com> wrote:
> > > Is the best course to create a recipe bbappend for the
> > > lighttpd_1.4.31.bb file that is being used? And can I just include a new
> > > file with the same name in my append and will it overwrite the old one,
> > > or do I need to create an actual patch file?
> >
> > So, since this config file is provided along with the original recipe, and
> > is already mentioned in SRC_URI and installed within do_install, you only
> > need to extend FILESEXTRAPATHS in your bbappend so that the system can
> > pick up your version of the file. Outright replacing the file is the easiest
> > way here rather than trying to patch it.
> >
> > So in your bbappend you would have:
> >
> > FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>
> how about if the lighttpd.conf file needs to be fetched (git or svn)
> instead added in the same repo as the recipe?
If fetching from git/svn then you'd just add an entry to SRC_URI, and the file
would be fetched into a subdirectory; you'd then just have a do_install() /
do_install_append() to install the version of the file from within that
subdirectory.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-10-10 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 20:30 How to customize a file coming from another recipe? Brad Litterell
2013-09-12 10:16 ` Paul Eggleton
2013-09-12 11:53 ` Nicolas Dechesne
2013-10-10 10:33 ` Paul Eggleton [this message]
2013-09-12 10:25 ` Andrea Galbusera
-- strict thread matches above, loose matches on Subject: below --
2013-09-11 19:24 Brad Litterell
2013-09-12 11:43 ` Tomas Frydrych
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=3776909.Wq363vMS5E@helios \
--to=paul.eggleton@linux.intel.com \
--cc=nicolas.dechesne@linaro.org \
--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.