Openembedded Core Discussions
 help / color / mirror / Atom feed
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: can i arbitrarily mix "meta-debian" recipes into my build?
Date: Fri, 28 Oct 2016 10:15:06 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1610281014560.4206@localhost.localdomain> (raw)
In-Reply-To: <CAJTo0LZxbiHqL4HeS28aLfmp-rgf_go0XNX-YQGSFmoNjooqHw@mail.gmail.com>

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

On Fri, 28 Oct 2016, Burton, Ross wrote:

>
> On 28 October 2016 at 09:00, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>         more silly questions ... just noticed that some of the recipes i'm
>       looking for exist under meta-debian; is there any issue with "mixing"
>       those recipes into my normal, poky-based, bleeding-edge image builds?
>
>
> meta-debian does a *lot* of stuff, some of which is very invasive,
> so I wouldn't recommend it.  If there's a recipe you want that is in
> meta-debian I'd use their recipe as a starting point and write a
> standalone recipe.

  understood.

rday

-- 

========================================================================
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:[~2016-10-28 14:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28  8:00 can i arbitrarily mix "meta-debian" recipes into my build? Robert P. J. Day
2016-10-28 14:09 ` Burton, Ross
2016-10-28 14:15   ` 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.20.1610281014560.4206@localhost.localdomain \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox