OE name usage

Khem Raj raj.khem at gmail.com
Wed Jul 31 05:29:17 UTC 2019


On Mon, Jun 24, 2019 at 2:08 AM Richard Purdie
<richard.purdie at linuxfoundation.org> wrote:
>
> On Sun, 2019-06-23 at 10:06 -0700, akuster808 wrote:
> > Sorry for cross posting.
> >
> > There are several applications that use distro identification to run
> > appropriate code paths.
> >
> > I would like to submit changes needed to identify the default OE
> > distro,  one of the identifiers is "openembedded".
>
> I'd like to understand more specifically what we're talking about and I
> think others will to understand this question. At first read I thought
> you were talking about one thing, now I suspect its another.
>
> There once was significant pushback on OE being "a distro", its a build
> system/architecture. Naming of things does tend to bring out strong
> views and personally, I believe calling everything X, regardless of
> what X is, just makes things worse as then nobody knows what you're
> talking about.
>
> "I used OE and OE to build OE and I'm now running OE on my system".
>
> That said, if we're talking about other applications in the wider
> software ecosystem which already identify debian, fedora and others,
> having a strategy there for OE might be good.
>

I have seen more examples of this kind where distro is redhat-like or
debian-like or gentoo-like and so on
in such cases I think openembedded makes sense, since thats directly
infra settings.

We dont have strong characteristics of OE derived distros  that
warrants a unique application programming
model.

> One challenge is OE is not one thing. If for example that software was
> using it to decide on init system, it would only be right for some set
> of OE built software so we need to be careful.
>
> >  That name does not belong to me so I am not sure what to do. Is
> > notification good enough or some sort of signoff  or approval by  the
> > OE Board, OE TSC or OE membership?
>
> I'd say a discussion on the openembedded-architecture list would be the
> right place with the TSC getting to mediate if consensus wasn't
> reached, the same as any other technical discussion. The branding piece
> may involve the board if they have a strong view and want to take the
> decision, they may choose to let the TSC handle it, its a grey area.
>
> I would say the OE membership delegated decision making to the board
> and TSC though.
>
> Cheers,
>
> Richard
>
> --
> _______________________________________________
> Openembedded-members mailing list
> Openembedded-members at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-members


More information about the tsc mailing list