Re: Package management DB in old-style SDK

[Denys Dmytriyenko <denis@denix.org>]

On Tue, Apr 19, 2016 at 10:35:29AM +1200, Paul Eggleton wrote:
> Hi Denys,
> 
> On Mon, 18 Apr 2016 18:14:55 Denys Dmytriyenko wrote:
> > I'm still using the old-style SDK (meta-toolchain) for our products due to
> > some code customizations in it and some of our use cases rely on the opkg
> > package management database being present in sysroots, so packages can be
> > manipulated in SDK with opkg command. It appears that /var/lib/opkg is now
> > empty and the package database is no longer supplied with the SDK.
> > 
> > I know about the new-style populate_sdk and the even newer Extensible SDK,
> > but not yet ready to convert our old use cases to that. Since there were
> > lots of changes around the way SDKs work in OE-Core in the past couple
> > releases, I'm failing to find the change that causes opkg DB to be missing
> > from the old style SDK. I'll appreciate any pointers in helping me debug
> > and/or fix this issue with my SDKs. Thanks.
> 
> As far as ipk is concerned I think it was this commit: 
> 
>   http://cgit.openembedded.org/openembedded-core/commit/?id=c8e0ec2da9ad4ce1c103966906a85f68c15400dd
> 
> Unfortunately it wasn't made optional.

Thanks, Paul!

Unfortunately, the change is in the library, which is quite difficult to 
override in another layer...

Will there be any objections for making that change optional with the default 
being like it is now, but with the ability to restore the old way with a 
variable?

-- 
Denys