[OE-core] [PATCH 0/7][PULL] Hob2 related oe-core changes

[Xu, Dongxiao]

Hi Richard,

> -----Original Message-----
> From: openembedded-core-bounces at lists.openembedded.org
> [mailto:openembedded-core-bounces at lists.openembedded.org] On Behalf Of
> Richard Purdie
> Sent: Saturday, January 07, 2012 12:28 AM
> To: Patches and discussions about the oe-core layer
> Subject: Re: [OE-core] [PATCH 0/7][PULL] Hob2 related oe-core changes
> 
> On Fri, 2012-01-06 at 17:04 +0800, Dongxiao Xu wrote:
> > Hi Richard,
> >
> > This pull request is the hob2 related oe-core changes.
> > Please help to review and pull.
> >
> > Note that this pull request has dependency on the hob related bitbake
> changes.
> >
> > Thanks,
> > Dongxiao
> >
> > The following changes since commit
> 4a85312568a6bb052cc511c15b4ae842ff7f8e59:
> >   Richard Purdie (1):
> >         image-mklibs/package_ipk: Remove bashisms
> >
> > are available in the git repository at:
> >
> >   git://git.pokylinux.org/poky-contrib dxu4/hob-oecore-changes
> >
> > http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dxu4/hob-oecore-
> > changes
> >
> > Dongxiao Xu (6):
> >   bblayers.conf.sample: Use ?= to set BBLAYERS
> >   image.bbclass: Use ?= to set LINGUAS_INSTALL
> 
> I merged these.

Thanks!

> 
> >   packageinfo.bbclass: add a new bbclass to pass package information
> 
> I still have quite a strong dislike of this code, its rather nasty to require this and I
> wish we could come up with a less ugly way to collect up this information.

I am sorry if this patch makes you feel uncomfortable.

Actually this approach was brought out early in the HOB2 design phase, and that time I didn't get explicit objection about it.
Refer to bug http://bugzilla.pokylinux.org/show_bug.cgi?id=1750, which is a M2 task.

Later we had some discussions of finding new way to dump all the available packages from server side.
Due to the schedule reason, we have to put it into M3. Refer to bug http://bugzilla.pokylinux.org/show_bug.cgi?id=1871.

But I think this approach is similar with buildhistory.bbclass. (Actually I am not aware there is buildhistory.bbclass exists when I wrote my code).
What the main difference is, buildhistory.bbclass writes the information into a local file, but packageinfo.bbclass emit the info as an event.

> 
> >   hob.bb: Add a empty image template
> >   hob-toolchain: add a new recipe hob-toolchain
> >   layers: add a new folder to put user added layers
> 
> I don't like these three. They're horribly hob specific and IMO shouldn't be in the
> general metadata. If there is no way to avoid them, they should perhaps go into
> a meta-hob layer directory to keep them separate from the rest of the system.

If we need to support the split of client and server, there is a principle that client GUI should not access any server directories or files.
Therefore HOB will not automatically generate any image bb files and copy it to meta directory.
This is the reason why we need to generate two empty image/toolchain files for the GUI to use.

If you do not like the name of hob.bb or hob-toolchain.bb, I can rename it to a generic one, like dummy-image.bb and dummy-toolchain.bb.
Actually putting them into meta-hob layer also works, but this requires the hob user to manually add meta-hob layer each time when he launches the HOB GUI. Of course we can defaultly add meta-hob layer into bblayers.conf.sample in meta-yocto layer if you think it is feasible.

> 
> I'm still puzzled how the layers directory helps. We deliberately support generic
> layer locations so forcing the user to place them in a particular place seems like
> a bit of a backwards step? :/.

We do not need the "layers" directory if users know where the layers are and then they can edit bblayers.conf.
And in non-split HOB case, users can still put their layers anywhere. HOB supports file browser and user can add layer by that.

But one new situation is, client GUI and server may run in different machines.
How could a client GUI user get the information what are the available layers in server?
I definitely welcome good suggestions.

Thanks,
Dongxiao

> 
> Cheers,
> 
> Richard
> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core