From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Trevor Woerner <twoerner@gmail.com>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>,
"Patches and discussions about the oe-core layer"
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] [RFC] Rename meta-openembedded to openembedded-extras
Date: Tue, 27 Feb 2018 16:56:57 +0000 [thread overview]
Message-ID: <63be8ac8a2744c64b18e252afd2e6307@XBOX02.axis.com> (raw)
In-Reply-To: <CAHUNapQYRJ=qNnQt8GT7eZ+m=iOdFDRWnY4Vuu4twB+VLA05jw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1664 bytes --]
Well, there is a benefit in having a common naming for layers in that it is possible to easily identify them programmatically. E.g., our setup will automatically take all checked out layers named “meta*” and add them to the bblayers.conf.sample file. That said, the name “meta” as it has been used, both for a specific layer (i.e., meta), as prefix for individual layers (e.g., meta-oe) and as prefix for a group of layers (e.g., meta-openembedded), is mostly confusing…
//Peter
From: openembedded-core-bounces@lists.openembedded.org [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of Trevor Woerner
Sent: den 27 februari 2018 16:27
To: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>; Patches and discussions about the oe-core layer <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [oe] [RFC] Rename meta-openembedded to openembedded-extras
On Fri, Feb 23, 2018 at 10:48 PM, Denys Dmytriyenko <denis@denix.org<mailto:denis@denix.org>> wrote:
On Thu, Feb 22, 2018 at 12:37:44PM -0800, akuster808 wrote:
> I think openembededd-core is incorrect. it should have been
> meta-openbedded-core or meta-core.
It does have a layer called just "meta" though...
In retrospect, using the word "meta" everywhere becomes useless. No layer contains actual sources and never should, so they're all "meta" data, it's redundant to have to say so in every layer's name (etc).
It would have been better to use that space to convey something meaningful, such as: "whether a layer was designed to be a bsp, a distro, something else, or a combination", or perhaps other meaningful information.
[-- Attachment #2: Type: text/html, Size: 5028 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Trevor Woerner <twoerner@gmail.com>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>,
"Patches and discussions about the oe-core layer"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [RFC] Rename meta-openembedded to openembedded-extras
Date: Tue, 27 Feb 2018 16:56:57 +0000 [thread overview]
Message-ID: <63be8ac8a2744c64b18e252afd2e6307@XBOX02.axis.com> (raw)
In-Reply-To: <CAHUNapQYRJ=qNnQt8GT7eZ+m=iOdFDRWnY4Vuu4twB+VLA05jw@mail.gmail.com>
Well, there is a benefit in having a common naming for layers in that it is possible to easily identify them programmatically. E.g., our setup will automatically take all checked out layers named “meta*” and add them to the bblayers.conf.sample file. That said, the name “meta” as it has been used, both for a specific layer (i.e., meta), as prefix for individual layers (e.g., meta-oe) and as prefix for a group of layers (e.g., meta-openembedded), is mostly confusing…
//Peter
From: openembedded-core-bounces@lists.openembedded.org [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of Trevor Woerner
Sent: den 27 februari 2018 16:27
To: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>; Patches and discussions about the oe-core layer <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [oe] [RFC] Rename meta-openembedded to openembedded-extras
On Fri, Feb 23, 2018 at 10:48 PM, Denys Dmytriyenko <denis@denix.org<mailto:denis@denix.org>> wrote:
On Thu, Feb 22, 2018 at 12:37:44PM -0800, akuster808 wrote:
> I think openembededd-core is incorrect. it should have been
> meta-openbedded-core or meta-core.
It does have a layer called just "meta" though...
In retrospect, using the word "meta" everywhere becomes useless. No layer contains actual sources and never should, so they're all "meta" data, it's redundant to have to say so in every layer's name (etc).
It would have been better to use that space to convey something meaningful, such as: "whether a layer was designed to be a bsp, a distro, something else, or a combination", or perhaps other meaningful information.
next prev parent reply other threads:[~2018-02-27 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 7:55 [RFC] Rename meta-openembedded to openembedded-extras Andrea Adami
2018-02-22 20:37 ` akuster808
2018-02-22 20:37 ` [OE-core] " akuster808
2018-02-24 3:48 ` [oe] " Denys Dmytriyenko
2018-02-24 3:48 ` [OE-core] " Denys Dmytriyenko
2018-02-27 15:27 ` [oe] " Trevor Woerner
2018-02-27 15:27 ` [OE-core] " Trevor Woerner
2018-02-27 16:56 ` Peter Kjellerstedt [this message]
2018-02-27 16:56 ` Peter Kjellerstedt
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=63be8ac8a2744c64b18e252afd2e6307@XBOX02.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=twoerner@gmail.com \
/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.