[bitbake-devel] PREFERRED_VERSION with % wildcard picking unexpected version

[Martin Jansa]

On Thu, Dec 10, 2015 at 12:27:36AM +0100, Nicolas Dechesne wrote:
> On Tue, Dec 1, 2015 at 6:13 AM, Andre McCurdy <armccurdy at gmail.com> wrote:
> > I have two recipes within a single layer:
> >
> >   stblinux_3.14-1.7.bb
> >   stblinux_3.14-1.8.bb
> >
> > If PREFERRED_VERSION_stblinux is set to "3.14%", then I would expect
> > the version 3.14-1.8 recipe to be selected, however 3.14-1.7 gets
> > selected instead.
> >
> > Reversing the order of files stored in pkg_pn[pn] seems to help. Is it
> > a reasonable solution?
> 
> 
> I have a somewhat similar issue..
> 
> in oe-core we have GCCVERSION set to 5.%, if I add meta-linaro layer
> which has gcc_5.1.bb (while OE has gcc_5.2.bb), I am seeing this:
> 
> $ bitbake -e gcc | grep ^PV
> PV="5.1.0"
> 
> While I would expect 5.2.0 to be picked up.
> 
> This patch does not fix this issue, btw.
> 
> If I remove gcc_5.1.bb from my layers, then I can see:
> 
> $ bitbake -e gcc | grep ^PV
> PV="5.2.0"

PREFERRED_VERSION was always meant to identify only 1 provider, the wildcard
is used only to say that you cannot specify the exact value - e.g. for
floating versions from SCM.

So if you have a layer with another recipe with version matching "5.%"
you're supposed to set PREFERRED_VERSION to more specific version.

See longer explanation in:
http://comments.gmane.org/gmane.comp.sysutils.bitbake.devel/1038

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/bitbake-devel/attachments/20151210/0ec5b057/attachment-0002.sig>