[oe] [meta-python][PATCH] meta-python: fix conf/layer.conf, follow typical structure

[Tim Orling]

> On Jul 30, 2014, at 3:30 AM, Paul Eggleton <paul.eggleton at linux.intel.com> wrote:
> 
>> On Wednesday 30 July 2014 10:12:05 Martin Jansa wrote:
>>> On Sat, Jul 26, 2014 at 10:34:35AM -0700, Tim Orling wrote:
>>> Ping.
>>> I haven't seen any comment on this patch at all.
>> 
>> I don't have strong opinion on this, but I don't like much the structure
>> with 1 recipe per directory, so I prefer single python directory with
>> all python modules together.
>> 
That is why I originally had meta-python/recipes-python/*.bb, to keep them all together...but we seem to always use one more sub-directory (e.g., meta-*/recipes-*/python/*.bb). I guess it's the extra subdir that bugs me, but that's just a minor annoyance. Having them all in one directory is ultimately preferred over one recipe per directory ;)

>> Also using the original structure from meta-oe has the advantage that
>> additional layers which were using include or require of some file from
>> python directory don't need any adaptation after meta-python was
>> separated (I've noticed it in one of our layers and that's why I've
>> submitted recipes-python -> recipes-devtools change).
> 
> Good point - I hadn't thought of this. FWIW I'm happy to have the meta-oe 
> directory structure retained in meta-python if it makes this easier.
> 
I had no idea that such collateral damage might occur. Now it makes sense why you reverted the structure.

Drop this patch in the dust bin.

--Tim