From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Jim Rafert <jimr@spectralogic.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: How do I create a recipe for laying down post-build config files?
Date: Tue, 10 Jun 2014 09:58:48 +0100 [thread overview]
Message-ID: <5396C8C8.4060303@dynamicdevices.co.uk> (raw)
In-Reply-To: <86196249137E0843B2E0673D4F731E0CAB521799@reactor.sldomain.com>
[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]
On 09/06/2014 22:44, Jim Rafert wrote:
> I'm trying to gather all my post-build tweaks into a recipe that will
> be built as part of an upper-level layer, so that they are installed
> after the meta layer is processed. Many of these could be
> accomplished as part of .bbappend files for the recipes that
> originally supply the config files, but I wanted to gather all my
> customizations in one spot, so that they're easy to find.
>
> The recipe doesn't actually build anything, so there's no do_build task.
>
> This is surely something that is commonly wanted.
>
> Here's my current recipe, in spectra-postbuild_0.1.bb.
>
> When I try to build an image, the build fails with
> ERROR: QA Issue: spectra-postbuild: Files/directories were installed
> but not shipped
> /RELEASE-NOTES.txt
>
> When I disable the installed-vs-shipped QA test, it fails later when
> it can't find a package file.
>
> I must be missing something critical here?
> SUMMARY = "Post processing of configuration files for SpectraOS"
> SECTION = "base"
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM =
> "file://${WORKDIR}/COPYRIGHT;md5=349c872e0066155e1818b786938876a4"
> RDEPENDS_${PN} = "initscripts"
> PR = "r0"
>
> SRC_URI = "file://inittab \
> file://fstab \
> file://rsyslog.conf \
> file://grub.cfg \
> file://mount.sh \
> file://RELEASE-NOTES.txt \
FILES_${PN} = "/RELEASE_NOTES.txt /Spectra-OS-Version "
RELEASE-NOTES vs RELEASE_NOTES
Cheers,
Alex
[-- Attachment #2: Type: text/html, Size: 3259 bytes --]
next prev parent reply other threads:[~2014-06-10 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 21:44 How do I create a recipe for laying down post-build config files? Jim Rafert
2014-06-10 8:30 ` Jens Lucius
2014-06-10 8:53 ` Paul Eggleton
2014-06-10 8:58 ` Alex J Lennon [this message]
2014-06-11 15:04 ` Jim Rafert
2014-06-10 15:02 ` Maxim Radugin
2014-06-13 22:02 ` Jim Rafert
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=5396C8C8.4060303@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=jimr@spectralogic.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.