Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: any issue with duplicate recipes spread over different layers?
Date: Sun, 30 Oct 2016 19:51:30 -0700	[thread overview]
Message-ID: <FB84115D-98FF-497A-8252-CD05EBA1E1E6@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1610300507330.27931@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1734 bytes --]


> On Oct 30, 2016, at 2:10 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> 
> 
>  not a burning issue, but while cataloguing some python recipes, i'm
> running across stuff like this:
> 
> $ find . -name python-six_1.10.0.bb
> ./meta-virtualization/recipes-devtools/python/python-six_1.10.0.bb
> ./openembedded-core/meta/recipes-devtools/python/python-six_1.10.0.bb
> ./meta-openembedded/meta-python/recipes-devtools/python/python-six_1.10.0.bb
> ...
> 
> $ find . -name python3-six_1.10.0.bb
> ./openembedded-core/meta/recipes-devtools/python/python3-six_1.10.0.bb
> ./meta-openembedded/meta-python/recipes-devtools/python/python3-six_1.10.0.bb
> ...
> 
>  so it appears the same(?) recipe for python-six appears in three
> different layers ... is there any effort expended to identify
> redundancy and remove it?

since its in OE-Core ( since July 2016 ), it would have been good if a
pull request to these layers went out atomically to remove them. But
its never too late, I encourage you to send removal patches to these
layers

> 
> rday
> 
> --
> 
> ========================================================================
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                        http://crashcourse.ca
> 
> Twitter:                                       http://twitter.com/rpjday
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> ========================================================================
> 
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

      reply	other threads:[~2016-10-31  2:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-30  9:10 any issue with duplicate recipes spread over different layers? Robert P. J. Day
2016-10-31  2:51 ` Khem Raj [this message]

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=FB84115D-98FF-497A-8252-CD05EBA1E1E6@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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