Re: migrating simple tarballs over to OE recipes?

[Martin Jansa <martin.jansa@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]

On Wed, Nov 23, 2016 at 01:00:12PM +0100, Ulf Magnusson wrote:
> On Wed, Nov 23, 2016 at 12:34 PM, Robert P. J. Day
> <rpjday@crashcourse.ca> wrote:
> > 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
> 
> bin_package.bbclass might be useful as well, especially if the files
> are already arranged like in the rootfs inside the tarballs.

If these files are overwriting files owned by some other packages, then
you will loose that customization when the package is upgraded by
package manager (unless those files are listed in CONFFILES). You need
to use RREPLACES at least.

> do_install() task that untars it into the root fs, yes?

? do_install installs them to $D not root fs which doesn't even exist yet.

You might also need to skip strip if there are also some binaries which are
already stripped, skip ldflash qa check if they don't have matching hash
type etc

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]