From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Chris Larson <chris_larson@mentor.com>,
Brian Avery <brian.avery@intel.com>,
bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] action: bitbake-layers new plugin to create a layer
Date: Mon, 24 Jul 2017 10:12:48 -0500 [thread overview]
Message-ID: <1500909168.2230.21.camel@linux.intel.com> (raw)
In-Reply-To: <15159983.UbMySVM7WB@peggleto-mobl.ger.corp.intel.com>
On Thu, 2017-07-20 at 17:58 +0200, Paul Eggleton wrote:
> (Brian reminded me of this, sorry for not replying earlier)
>
> On Monday, 19 June 2017 5:00:18 PM CEST
> leonardo.sandoval.gonzalez@linux.intel.com wrote:
> > From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
> >
> > Creates a simple layer with a example recipe, where the latter
> > has just a single task (do_build). Layer's license is MIT and
> > layer's priority defaults to 6. Recipe name and layer's priority
> > can changed specified through the command line.
>
> So I'm generally in favour of adding this functionality to bitbake-layers and
> making it more widely available in preference to yocto-layer. However, I'm a
> bit concerned about the template recipe - it really doesn't belong in bitbake.
> We could resolve that in one of two ways:
>
> 1) Look for the template within the metadata and provide one in OE-Core, or
>
> 2) Put the template *and* the plugin in OE-Core, since bitbake-layers should
> support loading plugins from the metadata
>
When I started this, I did not think about using OE-Core so this can be
more generic, meaning that there is no need for OE-Core metadata to have
this feature working.
Now with your inputs, I can see point 2 as an option so let I can work
in that direction if all agree.
Leo
> I don't mind which but I'd lean towards #2 since it will probably require less
> additional plumbing.
>
> Additionally we'll probably want to change "yocto-layer create" to call this
> and show a deprecation warning for the next release or two, and then drop it
> afterwards.
>
> Cheers,
> Paul
>
prev parent reply other threads:[~2017-07-24 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 15:00 [PATCH] action: bitbake-layers new plugin to create a layer leonardo.sandoval.gonzalez
2017-07-20 15:58 ` Paul Eggleton
2017-07-24 15:12 ` Leonardo Sandoval [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=1500909168.2230.21.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=brian.avery@intel.com \
--cc=chris_larson@mentor.com \
--cc=paul.eggleton@linux.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.