poky and OpenEmbedded (post-release)

poky and OpenEmbedded (post-release)

[Trevor Woerner]

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)?

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.

Re: poky and OpenEmbedded (post-release)

[Trevor Woerner]

On Fri, Apr 12, 2013 at 3:07 PM, Trevor Woerner <twoerner@gmail.com> wrote:
> You won't believe how
> I've poured over that page

(shoot! s/poured/pored)

Re: poky and OpenEmbedded (post-release)

[Denys Dmytriyenko]

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.

[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.
> 

Re: poky and OpenEmbedded (post-release)

[Martin Jansa]

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

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.

> [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

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

Re: poky and OpenEmbedded (post-release)

[Denys Dmytriyenko]

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