All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sven Ebenfeld <sven.ebenfeld@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: how to (yuck) add arbitrary external files into an image?
Date: Sun, 22 Feb 2015 03:55:39 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.11.1502220350280.14143@localhost> (raw)
In-Reply-To: <54E99779.2030405@gmail.com>

On Sun, 22 Feb 2015, Sven Ebenfeld wrote:

> Am 22.02.2015 um 09:33 schrieb Robert P. J. Day:
> >
> >   as much as this disturbs me, i was asked about the easiest way
> > to add arbitrary files scattered across the development host into
> > the final OE-generated image and, based on richard purdie's recent
> > clarification that *everything* that is listed in SRC_URI is
> > unloaded into WORKDIR, i suspect the easiest thing to do is create
> > a recipe where SRC_URI lists all of those files with "file:///",
> > and write an explicit install task that manually copies them, one
> > at a time, into their final location in D, yes?
> >
> >   i don't like this at all, but if it has to be done, is this at
> > least the "best" way to do it?
>
> I think the "best" way would be to create one recipe that collects
> these files and just installs them into $D. Then you could select
> this package in IMAGE_INSTALL as you described above.

  right ... isn't that what i was describing? or are you suggesting
some variation on that? i was envisioning a single recipe with a
SRC_URI loaded with "file:///" components.

> Another way is to use a ROOTFS_POSTPROCESS_COMMAND if you only need
> to do this for one image.

  ah, quite right, another simple option, thanks.

rday

p.s.  yes, i do understand that this is a tacky thing to do.
sometimes, you just need to do tacky.

-- 

========================================================================
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-22  8:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-22  8:33 how to (yuck) add arbitrary external files into an image? Robert P. J. Day
2015-02-22  8:46 ` Sven Ebenfeld
2015-02-22  8:55   ` Robert P. J. Day [this message]

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.1502220350280.14143@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sven.ebenfeld@gmail.com \
    /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.