parse/ConfHandler: Fix multiline variable corruption
authorRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 20 Jul 2011 21:51:23 +0000 (22:51 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 21 Jul 2011 10:09:47 +0000 (11:09 +0100)
commitd39ed67e3e743b09471e0254ff4375285f324c2d
treeab8468d616749c38c0cb2a92588191f43575cb18
parent1a000b9bfe99fcb9c013c89f6e083eb8adb1d862
parse/ConfHandler: Fix multiline variable corruption

When parsing multiline variables in conf files, the last character can
be accidentally removed. s2 contains new data read from the file which
may or may not end with the continuation character. It makes sense to
let the next loop iteration strip this if needed.

We don't often use multiline expressions in .conf files which is why I'd
imagine we haven't noticed this before. Most variables are quoted and
its the closing quotation which often disappears.

(Bitbake rev: 09a9146262d58dfe4a2ea4270026b90ae33f6c91)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/lib/bb/parse/parse_py/ConfHandler.py