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

2017-01-26 Thread Mariano Lopez
On 25/01/17 05:56, Richard Purdie wrote: > On Tue, 2017-01-24 at 11:52 -0700, Christopher Larson wrote: >> On Tue, Jan 24, 2017 at 1:37 AM, >> wrote: >>> From: Mariano Lopez >>> >>> opkg uses empty lines as separator for next

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

2017-01-25 Thread Richard Purdie
On Tue, 2017-01-24 at 11:52 -0700, Christopher Larson wrote: > > On Tue, Jan 24, 2017 at 1:37 AM, > wrote: > > From: Mariano Lopez > > > > opkg uses empty lines as separator for next package and if an ipk > > file was packaged with

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

2017-01-24 Thread Christopher Larson
On Tue, Jan 24, 2017 at 1:37 AM, wrote: > From: Mariano Lopez > > 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,

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

2017-01-24 Thread mariano . lopez
From: Mariano Lopez 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