Re: [PATCH 1/1] package_ipk.bbclass: Add check for empty lines in DESCRIPTION

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Tue, 2017-01-24 at 11:52 -0700, Christopher Larson wrote:
> 
> On Tue, Jan 24, 2017 at 1:37 AM, <mariano.lopez@linux.intel.com>
> wrote:
> > From: Mariano Lopez <mariano.lopez@linux.intel.com>
> > 
> > opkg uses empty lines as separator for next package and if an ipk
> > file was packaged with empty lines in DESCRIPTION opkg won't be
> > able to handle such ipk file, this happens at execution time.
> > 
> > This commit will add a check for empty lines in DESCRIPTION when
> > generating to ipk package to avoid this issue.
> > 
> > [YOCTO #10677]
> > 
> > Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com>
> > 
> Could it handle a line with just a space, or a period? Could you not
> replace the lines with that instead, rather than aborting?

FWIW package_deb uses ".".

Also, please use bb.fatal() calls with caution, I just removed several
from that class. In this case its perhaps ok but often the correct
thing to do is raise an exception of some kind. This means bitbake will
generate a usable traceback rather than simply printing the fatal
message. In this case the message is probably fine but there were
several cases where a traceback was a much better idea as the fatal
message wasn't enough to debug with.

Cheers,

Richard