From: Denys Dmytriyenko <denis@denix.org>
To: akuster808 <akuster808@gmail.com>
Cc: 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: Fri, 23 Feb 2018 22:48:07 -0500 [thread overview]
Message-ID: <20180224034807.GF2786@denix.org> (raw)
In-Reply-To: <0bb858dc-a43f-ae14-01c9-2a42855e4409@gmail.com>
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
next prev parent reply other threads:[~2018-02-24 3:48 UTC|newest]
Thread overview: 5+ 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-24 3:48 ` Denys Dmytriyenko [this message]
2018-02-27 15:27 ` [oe] " Trevor Woerner
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=20180224034807.GF2786@denix.org \
--to=denis@denix.org \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox