Re: How do I change the "Architecture" of a package?

[Mike Looijmans <mike.looijmans@topic.nl>]

On 12/31/2014 08:13 PM, Mike Looijmans wrote:
> On 30-12-2014 18:59, Paul Barker wrote:
>> On Tue, Dec 30, 2014 at 04:24:34PM +0100, Mike Looijmans wrote:
>>> What if the architecture of a package was accidentally left at its
>>> default, but it should have been "all" for example?
>>>
>>> Just putting "inherit allarch" or simply PACKAGE_ARCH="all" into the
>>> recipe is not enough. You get stuck with a "more specific" older
>>> version, so that no device wants to upgrade to the newer version
>>> that's "all" architecture compatible.
>>>
>>
>> What package manager are you using on the device? If you're using opkg
>> it should
>> prioritise by version not arch unless the command line option
>> '--prefer-arch-to-version' is passed. If you're using opkg and it's
>> not doing
>> that, let me know and I'll look into it when I get chance to.
>
> It's opkg.
>
> But on closer inspection I noticed that the "git" version is also
> mysteriously reset to 0, so that the package also gets a lower version
> number instead of a higher one. Seems to be the PR server borking things
> again or so, I'll have to investigate that next year...

Weird, something in OE killed "gitpkgv".

in the recipe, I have this:

inherit gitpkgv
PV = "2.0+git${SRCPV}"
PKGV = "2.0+git${GITPKGV}"


$ bitbake enigma2-plugin-extensions-autobackup -e | grep PKGV

delivers correct information:

PKGV="2.0+git68+2e7a1db"
GITPKGVTAG="0.0-68-g2e7a1db"
GITPKGV="68+2e7a1db"


But after building and deploying the package, the version number will 
eventually end up being this one:

2.0+git5+2e7a1db509-r0.2


What in OE is replacing a perfectly good PKGV tag with something 
completely different bearing no relation whatsoever? Even the number of 
digits in the git tag differs from the one I put in the recipe!

Even if I put some random text into PKGV, it gets replaced.

-- 
Mike Looijmans