From: Denys Dmytriyenko <denis@denix.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: poky@yoctoproject.org
Subject: Re: poky and OpenEmbedded (post-release)
Date: Fri, 12 Apr 2013 15:54:37 -0400 [thread overview]
Message-ID: <20130412195437.GB3757@denix.org> (raw)
In-Reply-To: <20130412194229.GU2477@jama>
On Fri, Apr 12, 2013 at 09:42:29PM +0200, Martin Jansa wrote:
> On Fri, Apr 12, 2013 at 03:31:16PM -0400, Denys Dmytriyenko wrote:
> > On Fri, Apr 12, 2013 at 03:07:00PM -0400, Trevor Woerner wrote:
> > > Many thanks to Denys for pointing me to
> > > http://openembedded.org/wiki/OpenEmbedded-Core. You won't believe how
> > > I've poured over that page and how many "lights have gone on" while
> > > reading it (over and over).
> > >
> > > If poky started as a fork of OE but is now a distribution, wouldn't it
> > > make sense to remove the "meta" directory from poky and simply have
> > > people add openembedded-core as a layer (as they would any other
> > > layer)?
> >
> > I believe that was suggested few times before (and other distros are doing
> > exactly that - i.e. assembling their distros from layers), but Poky developers
> > prefer their distro to be already pre-assembled for ease of use. Besides
> > openembedded-core layer, there're also bitbake and meta-yocto inside Poky. It
> > maybe confusing at first, but think of it as being pre-assembled from bitbake+
> > oe-core + meta-yocto and saved into a single repository.
> >
> > Well, at least it saves Poky from needing to provide setup tools to download
> > and assemble different layers from different repositories. Otherwise you would
> > need something like our oe-layersetup[1] tool for Arago or setup-scripts for
> > Angstrom etc.
>
> But on the other hand they wouldn't need to send slightly different
> (path prefix) patchsets for poky and for oe-core/bitbake/meta-yocto.
Yes, indeed! So, a slightly easier user experience for the price of a slight
maintenance overhead. :)
--
Denys
> > [1] git://arago-project.org/git/projects/oe-layersetup.git
> >
> > --
> > Denys
> >
> > > Or am I going down the wrong path with this thought?
> > >
> > > Of course it might be confusing having, potentially, both an
> > > openembedded-core and a meta-openembedded layer, but it seems like
> > > having the "meta" directory in poky is redundant, given that it is
> > > already its own layer in openembedded-core.
> > >
> > _______________________________________________
> > poky mailing list
> > poky@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/poky
>
> --
> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
prev parent reply other threads:[~2013-04-12 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 19:07 poky and OpenEmbedded (post-release) Trevor Woerner
2013-04-12 19:10 ` Trevor Woerner
2013-04-12 19:31 ` Denys Dmytriyenko
2013-04-12 19:42 ` Martin Jansa
2013-04-12 19:54 ` Denys Dmytriyenko [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=20130412195437.GB3757@denix.org \
--to=denis@denix.org \
--cc=martin.jansa@gmail.com \
--cc=poky@yoctoproject.org \
/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.