From: "André Draszik" <git@andred.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] autoconf-archive: inherit allarch and fix package splitting
Date: Mon, 13 Nov 2017 08:54:09 +0000 [thread overview]
Message-ID: <1510563249.4049.33.camel@andred.net> (raw)
In-Reply-To: <62db9387c3ee71f4bed87a7a546afdf927ba5ac0.1510550741.git.Qi.Chen@windriver.com>
Hi,
On Mon, 2017-11-13 at 13:26 +0800, Chen Qi wrote:
> autoconf-archive is a set of common m4 macros, it should be allarch,
> just like it is on other distros.
I have found previously that when changing a recipe to produce more generic
output, like in this case, and the old binary package is still in deploy/,
then the package manager would always pick the more specific version, even
if a more recent (by package version) exists in deploy. In my case I was
moving from PACKAGE_ARCH=${MACHINE_ARCH} to PACKAGE_ARCH=${TUNE_PKGARCH},
but I guess it'll be the same here.
What is the correct way to deal with that other that cleansstate?
Cheers,
Andre'
next prev parent reply other threads:[~2017-11-13 8:54 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 [this message]
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
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=1510563249.4049.33.camel@andred.net \
--to=git@andred.net \
--cc=openembedded-core@lists.openembedded.org \
/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