[OE-core] [PATCH 1/1] package.bbclass: Allow overriding of debugedit starting path

[Peter Seebach]

On Wed, 11 Jul 2012 18:36:50 +0100
Richard Purdie <richard.purdie at linuxfoundation.org> wrote:

> It should all use 4 space for python functions. There is however a
> twist which is due to the way we handle _prepend and _append. Those
> prepends and appends have whitespace too and I seem to remember
> issues with whitespace matching.
> 
> Yes, this is horrible. This is why that file hasn't been touched for
> whitespace though.

noooooooo

That hurts so much.

Okay, crazy thought.  Imagine that we were to make a modified parser,
with the following behavior:

Whenever reading a python function, count the indentation of the first
line (N), then replace every N spaces of indentation with 4 spaces.

If this worked, it would make it possible to start fixing stuff.

DISCLAIMER:  Due to Reasons, I have slept about 15 minutes out of the
last day, also I'm sick. When I say "crazy thought", I do not kid.

Anyway:  Anyone have other thoughts/comments on the possible starting
path fixup? I am pretty sure that it is sufficient for all real cases,
with the one exception being prebuilts where the debug path names are
unreasonably short.  (I theorize that a more advanced debugedit could
be written which could handle those by rewriting files.  I nominate
someone else to try to actually do it.)

My initial theory that I'd need to be able to specify the destination
path evaporates with the realization that we can always move source
files to whatever path we want them in; it's just that it's nicer for
everyone if the debug source files are always in the standard locations,
give or take, no matter how they were built.

-s
-- 
Listen, get this.  Nobody with a good compiler needs to be justified.