[oe] [meta-oe] [PATCH] xserver-common: remove extraneous BSP customizations

[Otavio Salvador]

On Sat, Jan 7, 2012 at 14:37, Andrea Adami <andrea.adami at gmail.com> wrote:

> > I've already explained to you to use VIRTUAL_RUNTIME vars.
>
> Sorry but this is not enough in order to obtain a core-image-sato with
> working xserver on first run.
> The meta-oe layer is 'toxic' in that regard.


Agreed; that's why I said you could fix x11-common and make it work so we
can drop xserver-common from meta-oe.


> >> 4) xserver-common is an old recipe coming from the oe-classic times,
> >> designed to work with gpe environments and targeting mostly kdrive.
> >> Thius recipe contains alot of BSP code.
> >
> > Yes and those patches you've removed are not making it worse, upstream
> > script contains a lot of BSP code already and those patches are just
> > making it more complete (think about it as patch which should be applied
> > upstream not in BSP layer).
> >
>
> Those patches ought to be sent upstream long agoi...
> I'm sure Florian will apply almost immediately once aware.
>
>
> >> 5) today, if one builds core-image-sato distroless for zaurus qvga
> >> using meta-oe the xserver won't start because of the bad settings
> >> provided by the recipe.
> >
> > see A3).
> >
> >> So, I already sent a msg in that regard before (
> >>
> http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-October/035564.html
> >> ) and now I'm trying to help cleaning both sides.
> >> The patch for x11-common was taken in oe-core but this one for meta-oe
> >> is unexpectedly under discussion.
> >> BE sure my intentions are not to increase maintenance burden, on the
> >> opposite I'd like neutral/sane defaults and patches to override those
> >> in the BSP layers.
> >
> > burden is to force people to fix recipe which should be removed instead.
> >
>
> This is my last reply to this thread.
> Again I'm sorry to force maintainers of external layers to react and
> make hanges but there is anything wrong with this.
> We did agree the policy of meta-oe is the same of oe-core, thus no BSP
> code is allowed. Stop.
> I'd expect the maintainer agrees.
>

I think you missunderstood it. We are not saying it shouldn't be removed
but we're saying we ought to do that in another way.

This will be removed all together with xserver-common in the move to
x11-common but for this, x11-common need to have the improvements done on
xserver-common merged.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio at ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br