From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: migrating simple tarballs over to OE recipes?
Date: Wed, 23 Nov 2016 06:34:02 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.20.1611230633180.8293@ca624034.mitel.com> (raw)
In-Reply-To: <CAJTo0LZvk-Ssv3Bc5rSYSuYCm2rQma4Vwv2jvh5zdE7cCPE0Vg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
On Wed, 23 Nov 2016, Burton, Ross wrote:
>
> On 23 November 2016 at 10:42, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> colleague has a pile of tarballs that were used to customize an x86
> centos system, wants to move all that to OE with as little fuss as
> possible, i guess the simplest way is to just create recipes that have
> the same tarball in the files/ directory, and write a trivial
> do_install() task that untars it into the root fs, yes?
>
>
> Pretty much, yeah.
>
> If you've a large pile and they're all effectively the same then a
> little class can automate it even more.
already going down that road, just wanted to make sure i hadn't
overlooked something obvious.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2016-11-23 11:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 10:42 migrating simple tarballs over to OE recipes? Robert P. J. Day
2016-11-23 11:21 ` Burton, Ross
2016-11-23 11:34 ` Robert P. J. Day [this message]
2016-11-23 12:00 ` Ulf Magnusson
2016-11-23 15:05 ` Martin Jansa
2016-11-23 16:52 ` Robert P. J. Day
2016-11-24 16:50 ` Burton, Ross
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.20.1611230633180.8293@ca624034.mitel.com \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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.