Re: [meta-oe,thud][PATCH 0/6] libiio: backports from master

[Martin Siegumfeldt <mns@gomspace.com>]

On Tue, Nov 05, 2019 at 03:55:12PM +0200, Adrian Bunk wrote:
> On Tue, Nov 05, 2019 at 01:00:25PM +0100, Martin Siegumfeldt wrote:
> > Backport libiio patches from master bumping libiio to v0.18 and
>
> Upgrading on an upstream stable branch can be OK,
> especially when this is the lowest risk way to fix CVEs.
>
> But upgrading to new releases on the master branch is usually not worth
> the regression risk - the default is to avoid changes in OE stable branches.
>
> > allows building python3 bindings
> >...
>
> No new features in OE stable branches.

And even more important:
No removal of features users might be using.

Like the Python2 bindings in this case.

cu
Adrian

--

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


Hi Adrian,

I see - can you please confirm that this constraint applies to Zeus and Warrior (which is also stable according to https://wiki.yoctoproject.org/wiki/Releases)

What I am trying to achieve (from the thud baseline) is to get libiio python3 bindings built. Now, most of the variables from libiio_git.bb can be overridden in an append file, except for the 'inherit pythonnative' statement that dictates python2 bindings to be packaged. AFAICS, this leaves me with the only option of, not appending, but to define my own (.bb) recipe in my layer taking precedence over the one from meta-openembedded - a suboptimal solution I guess.

Anything I am missing?

Thanks,
Martin