From: "André Draszik" <git@andred.net>
To: Robert Yang <liezhi.yang@windriver.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] autoconf-archive: inherit allarch and fix package splitting
Date: Wed, 15 Nov 2017 09:06:47 +0000 [thread overview]
Message-ID: <1510736807.4049.75.camel@andred.net> (raw)
In-Reply-To: <4a8c2156-35df-8786-31c8-b35b8a6588d3@windriver.com>
Hi,
On Wed, 2017-11-15 at 10:23 +0800, Robert Yang wrote:
>
> On 11/14/2017 10:02 PM, André Draszik wrote:
> > Is that an ipk / OPKG issue? Should something be removing the old
> > packages
> > from deploy?
>
> I tried PACKAGE_CLASSES = "package_ipk", I got the same result as ross:
OK, so I tried with autoconf-archive myself now. I get the same result as
you two.
But - When moving a recipe from MACHINE_ARCH to TUNE_PKGARCH then the old
package is not removed.
[...]
> I guess something is wrong with your build.
To summarise:
- moving a recipe from TUNE_PKGARCH to allarch removes the old package
- moving a recipe from MACHINE_ARCH to TUNE_PKGARCH *doesn't* remove the old
package.
Where would I start looking?
Cheers,
Andre'
next prev parent reply other threads:[~2017-11-15 9:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 5:26 [PATCH 0/1] autoconf-archive: inherit allarch and fix package splitting Chen Qi
2017-11-13 5:26 ` [PATCH 1/1] " Chen Qi
2017-11-13 8:54 ` André Draszik
2017-11-13 10:12 ` Martin Jansa
2017-11-13 10:34 ` opkg --prefer-arch-to-version (was: Re: [PATCH 1/1] autoconf-archive: inherit allarch and fix package splitting) André Draszik
2017-11-13 12:05 ` Martin Jansa
2017-11-13 11:54 ` [PATCH 1/1] autoconf-archive: inherit allarch and fix package splitting Robert Yang
2017-11-14 10:16 ` André Draszik
2017-11-14 11:34 ` Burton, Ross
2017-11-14 11:41 ` Burton, Ross
2017-11-14 14:02 ` André Draszik
2017-11-15 2:23 ` Robert Yang
2017-11-15 9:06 ` André Draszik [this message]
2017-11-15 9:24 ` Robert Yang
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=1510736807.4049.75.camel@andred.net \
--to=git@andred.net \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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