[OE-core] should a "*git.bb" recipe lock that recipe to a fixed version?

Robert P. J. Day rpjday at crashcourse.ca
Sun Oct 30 12:25:19 UTC 2016


  not sure if i should have noticed this before, but i was building a
number of python modules, and my collection of layers gave me two
possibilities for python-django:

  * python-django_git.bb      (meta-openstack)
  * python-django_1.9.7.bb    (meta-python)

  i simply assumed that any "git"-versioned recipe would typically
take precedence over a fixed version recipe, so i was surprised to see
that what was built was python-django-1.8.6. huh?

  then i looked at the recipe from meta-openstack, and it contained
the lines:

  PV = "1.8.6"
  SRCREV = "80b7e9d09f2d23209b591288f9b2cf3eb3d927c8"

  SRC_URI = " \
      git://github.com/django/django.git;branch=stable/1.8.x \
      "

am i right in being a bit confused by that? i checked out the github
repo, and it has branches "stable/1.8.x", and also "stable/1.9.x" and
"stable/1.10.x". so what is that supposed to mean?

  am i right in assuming that a "git" recipe will (in the absence of
any PREFERRED_VERSION settings or other overriding settings) always be
considered before a fixed version recipe? and is that why i got this
(for me) unexpected result?

  i note at least one recipe in oe-core that has that same property:

  libepoxy_git.bb

which contains:

  SRC_URI = " \
    git://github.com/anholt/libepoxy.git \
    file://0001-select-platforms-based-on-configuration-results.patch \
    file://0002-add-an-option-to-disable-glx-support.patch \
    file://no-need-for-python3.patch \
  "
  SRCREV="e2c33af5bfcfc9d168f9e776156dd47c33f428b3"
  PV = "1.3.1"

it is just my responsibility to notice that, and use PREFERRED_VERSION
to make sure i get the version i want?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================




More information about the Openembedded-core mailing list