* [RFC] Rename meta-openembedded to openembedded-extras @ 2018-02-22 7:55 Andrea Adami 2018-02-22 20:37 ` [OE-core] " akuster808 0 siblings, 1 reply; 9+ messages in thread From: Andrea Adami @ 2018-02-22 7:55 UTC (permalink / raw) To: OpenEmbedded Devel List, Patches and discussions about the oe-core layer All, it seems there is some consensus about reordering/cleaning the "OpenEmbedded layers". I think that before starting any cleaning *inside* we should finally clean up the confusion about meta-oe meta-openembedded openembedded-layers, etc.. I think it would be advisable to rename the repository from meta-openembedded to openembedded-extras, matching the openembedded-core naming schema. Regards Andrea P.S. One layer of this repo would be the (in)famous meta-oe. I can't imagine right now a definition for it: it contains old versions of oe-core recipes, expunged recipes, tools and libraries needed by other layers (i.e. tslib), etc. etc. This one will need a separate thread. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [RFC] Rename meta-openembedded to openembedded-extras 2018-02-22 7:55 [RFC] Rename meta-openembedded to openembedded-extras Andrea Adami @ 2018-02-22 20:37 ` akuster808 0 siblings, 0 replies; 9+ messages in thread From: akuster808 @ 2018-02-22 20:37 UTC (permalink / raw) To: Andrea Adami, OpenEmbedded Devel List, Patches and discussions about the oe-core layer On 02/21/2018 11:55 PM, Andrea Adami wrote: > All, > it seems there is some consensus about reordering/cleaning the > "OpenEmbedded layers". > > I think that before starting any cleaning *inside* we should finally > clean up the confusion about meta-oe meta-openembedded > openembedded-layers, etc.. > > I think it would be advisable to rename the repository from > meta-openembedded to openembedded-extras, matching the > openembedded-core naming schema. Renaming an existing repo will cause more damage than what benefit one thinks it may solve. I think openembededd-core is incorrect. it should have been meta-openbedded-core or meta-core. - armin > > Regards > Andrea > > > P.S. > One layer of this repo would be the (in)famous meta-oe. > I can't imagine right now a definition for it: it contains old > versions of oe-core recipes, expunged recipes, tools and libraries > needed by other layers (i.e. tslib), etc. etc. > This one will need a separate thread. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [OE-core] [RFC] Rename meta-openembedded to openembedded-extras @ 2018-02-22 20:37 ` akuster808 0 siblings, 0 replies; 9+ messages in thread From: akuster808 @ 2018-02-22 20:37 UTC (permalink / raw) To: Andrea Adami, OpenEmbedded Devel List, Patches and discussions about the oe-core layer On 02/21/2018 11:55 PM, Andrea Adami wrote: > All, > it seems there is some consensus about reordering/cleaning the > "OpenEmbedded layers". > > I think that before starting any cleaning *inside* we should finally > clean up the confusion about meta-oe meta-openembedded > openembedded-layers, etc.. > > I think it would be advisable to rename the repository from > meta-openembedded to openembedded-extras, matching the > openembedded-core naming schema. Renaming an existing repo will cause more damage than what benefit one thinks it may solve. I think openembededd-core is incorrect. it should have been meta-openbedded-core or meta-core. - armin > > Regards > Andrea > > > P.S. > One layer of this repo would be the (in)famous meta-oe. > I can't imagine right now a definition for it: it contains old > versions of oe-core recipes, expunged recipes, tools and libraries > needed by other layers (i.e. tslib), etc. etc. > This one will need a separate thread. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [oe] [RFC] Rename meta-openembedded to openembedded-extras 2018-02-22 20:37 ` [OE-core] " akuster808 @ 2018-02-24 3:48 ` Denys Dmytriyenko -1 siblings, 0 replies; 9+ messages in thread From: Denys Dmytriyenko @ 2018-02-24 3:48 UTC (permalink / raw) To: akuster808 Cc: OpenEmbedded Devel List, Patches and discussions about the oe-core layer On Thu, Feb 22, 2018 at 12:37:44PM -0800, akuster808 wrote: > On 02/21/2018 11:55 PM, Andrea Adami wrote: > > All, > > it seems there is some consensus about reordering/cleaning the > > "OpenEmbedded layers". > > > > I think that before starting any cleaning *inside* we should finally > > clean up the confusion about meta-oe meta-openembedded > > openembedded-layers, etc.. > > > > I think it would be advisable to rename the repository from > > meta-openembedded to openembedded-extras, matching the > > openembedded-core naming schema. > Renaming an existing repo will cause more damage than what benefit one > thinks it may solve. Agree. > 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... > - armin > > > > Regards > > Andrea > > > > > > P.S. > > One layer of this repo would be the (in)famous meta-oe. > > I can't imagine right now a definition for it: it contains old > > versions of oe-core recipes, expunged recipes, tools and libraries > > needed by other layers (i.e. tslib), etc. etc. > > This one will need a separate thread. > > > -- > _______________________________________________ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [OE-core] [RFC] Rename meta-openembedded to openembedded-extras @ 2018-02-24 3:48 ` Denys Dmytriyenko 0 siblings, 0 replies; 9+ messages in thread From: Denys Dmytriyenko @ 2018-02-24 3:48 UTC (permalink / raw) To: akuster808 Cc: OpenEmbedded Devel List, Patches and discussions about the oe-core layer On Thu, Feb 22, 2018 at 12:37:44PM -0800, akuster808 wrote: > On 02/21/2018 11:55 PM, Andrea Adami wrote: > > All, > > it seems there is some consensus about reordering/cleaning the > > "OpenEmbedded layers". > > > > I think that before starting any cleaning *inside* we should finally > > clean up the confusion about meta-oe meta-openembedded > > openembedded-layers, etc.. > > > > I think it would be advisable to rename the repository from > > meta-openembedded to openembedded-extras, matching the > > openembedded-core naming schema. > Renaming an existing repo will cause more damage than what benefit one > thinks it may solve. Agree. > 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... > - armin > > > > Regards > > Andrea > > > > > > P.S. > > One layer of this repo would be the (in)famous meta-oe. > > I can't imagine right now a definition for it: it contains old > > versions of oe-core recipes, expunged recipes, tools and libraries > > needed by other layers (i.e. tslib), etc. etc. > > This one will need a separate thread. > > > -- > _______________________________________________ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [oe] [RFC] Rename meta-openembedded to openembedded-extras 2018-02-24 3:48 ` [OE-core] " Denys Dmytriyenko @ 2018-02-27 15:27 ` Trevor Woerner -1 siblings, 0 replies; 9+ messages in thread From: Trevor Woerner @ 2018-02-27 15:27 UTC (permalink / raw) To: OpenEmbedded Devel List, Patches and discussions about the oe-core layer [-- Attachment #1: Type: text/plain, Size: 737 bytes --] On Fri, Feb 23, 2018 at 10:48 PM, Denys Dmytriyenko <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: 1188 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [OE-core] [RFC] Rename meta-openembedded to openembedded-extras @ 2018-02-27 15:27 ` Trevor Woerner 0 siblings, 0 replies; 9+ messages in thread From: Trevor Woerner @ 2018-02-27 15:27 UTC (permalink / raw) To: OpenEmbedded Devel List, Patches and discussions about the oe-core layer On Fri, Feb 23, 2018 at 10:48 PM, Denys Dmytriyenko <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. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [oe] [RFC] Rename meta-openembedded to openembedded-extras 2018-02-27 15:27 ` [OE-core] " Trevor Woerner @ 2018-02-27 16:56 ` Peter Kjellerstedt -1 siblings, 0 replies; 9+ messages in thread From: Peter Kjellerstedt @ 2018-02-27 16:56 UTC (permalink / raw) To: Trevor Woerner, OpenEmbedded Devel List, Patches and discussions about the oe-core layer [-- 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 --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [OE-core] [RFC] Rename meta-openembedded to openembedded-extras @ 2018-02-27 16:56 ` Peter Kjellerstedt 0 siblings, 0 replies; 9+ messages in thread From: Peter Kjellerstedt @ 2018-02-27 16:56 UTC (permalink / raw) To: Trevor Woerner, OpenEmbedded Devel List, Patches and discussions about the oe-core layer 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. ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2018-02-27 16:56 UTC | newest] Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 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 ` [oe] " Peter Kjellerstedt 2018-02-27 16:56 ` [OE-core] " Peter Kjellerstedt
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.