[OE-core] any issue with duplicate recipes spread over different layers?

[Khem Raj]

> On Oct 30, 2016, at 2:10 AM, Robert P. J. Day <rpjday at 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 at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20161030/7cf3f70a/attachment-0002.sig>