From: Denys Dmytriyenko <denis@denix.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Package management DB in old-style SDK
Date: Fri, 22 Apr 2016 14:07:17 -0400 [thread overview]
Message-ID: <20160422180717.GT16135@denix.org> (raw)
In-Reply-To: <1922089.IxRdTHIprx@peggleto-mobl.ger.corp.intel.com>
On Tue, Apr 19, 2016 at 01:38:23PM +1200, Paul Eggleton wrote:
> On Mon, 18 Apr 2016 21:01:27 Denys Dmytriyenko wrote:
> > 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=c8e0ec2da9ad4c
> > > e1c103966906a85f68c15400dd>
> > > 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?
>
> As long as we make it have the same effect across the three different package
> managers, no objection from me at least. Thinking about it we could even make
> it switch based on package-management being in SDKIMAGE_FEATURES and then it
> would be consistent with how it works for images as well.
Hi, Paul,
I submitted a patch yesterday to make the discussed change - can you please
review and provide feedback? Thanks.
--
Denys
prev parent reply other threads:[~2016-04-22 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 22:14 Package management DB in old-style SDK Denys Dmytriyenko
2016-04-18 22:35 ` Paul Eggleton
2016-04-19 1:01 ` Denys Dmytriyenko
2016-04-19 1:38 ` Paul Eggleton
2016-04-19 2:19 ` Christopher Larson
2016-04-19 2:20 ` Christopher Larson
2016-04-22 18:07 ` Denys Dmytriyenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160422180717.GT16135@denix.org \
--to=denis@denix.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox