mirror of
git://git.yoctoproject.org/poky.git
synced 2025-07-19 12:59:02 +02:00
c9565b89d0
The variable SRCPV is deprecated since 4.3. Instead of including SRCPV in PV, including the sign "+" is enough for bitbake to add the source control information to PKGV during the packaging phase. Update the documentation for SRCPV and the places where it was used. When instructions previously referred to SRCPV, replace by mentioning to include "+" in the assignment. In most examples, "+git" is added to PV as it is the most popular SCM. Simply adding "+" is also possible, although it is better practice to include the SCM name, so give that example. Update the gcompat example with l3afpad as it didn't include "+git" in its PV definition anymore. (From yocto-docs rev: ee16c96202e5027d1a8d7e89e11c25f127c78326) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
71 lines
2.4 KiB
ReStructuredText
71 lines
2.4 KiB
ReStructuredText
.. SPDX-License-Identifier: CC-BY-SA-2.0-UK
|
|
|
|
Using an External SCM
|
|
*********************
|
|
|
|
If you're working on a recipe that pulls from an external Source Code
|
|
Manager (SCM), it is possible to have the OpenEmbedded build system
|
|
notice new recipe changes added to the SCM and then build the resulting
|
|
packages that depend on the new recipes by using the latest versions.
|
|
This only works for SCMs from which it is possible to get a sensible
|
|
revision number for changes. Currently, you can do this with Apache
|
|
Subversion (SVN), Git, and Bazaar (BZR) repositories.
|
|
|
|
To enable this behavior, the :term:`PV` of
|
|
the recipe needs to include a ``+`` sign in its assignment.
|
|
Here is an example::
|
|
|
|
PV = "1.2.3+git"
|
|
|
|
:term:`Bitbake` later includes the source control information in :term:`PKGV`
|
|
during the packaging phase.
|
|
|
|
Then, you can add the following to your
|
|
``local.conf``::
|
|
|
|
SRCREV:pn-PN = "${AUTOREV}"
|
|
|
|
:term:`PN` is the name of the recipe for
|
|
which you want to enable automatic source revision updating.
|
|
|
|
If you do not want to update your local configuration file, you can add
|
|
the following directly to the recipe to finish enabling the feature::
|
|
|
|
SRCREV = "${AUTOREV}"
|
|
|
|
The Yocto Project provides a distribution named ``poky-bleeding``, whose
|
|
configuration file contains the line::
|
|
|
|
require conf/distro/include/poky-floating-revisions.inc
|
|
|
|
This line pulls in the
|
|
listed include file that contains numerous lines of exactly that form::
|
|
|
|
#SRCREV:pn-opkg-native ?= "${AUTOREV}"
|
|
#SRCREV:pn-opkg-sdk ?= "${AUTOREV}"
|
|
#SRCREV:pn-opkg ?= "${AUTOREV}"
|
|
#SRCREV:pn-opkg-utils-native ?= "${AUTOREV}"
|
|
#SRCREV:pn-opkg-utils ?= "${AUTOREV}"
|
|
SRCREV:pn-gconf-dbus ?= "${AUTOREV}"
|
|
SRCREV:pn-matchbox-common ?= "${AUTOREV}"
|
|
SRCREV:pn-matchbox-config-gtk ?= "${AUTOREV}"
|
|
SRCREV:pn-matchbox-desktop ?= "${AUTOREV}"
|
|
SRCREV:pn-matchbox-keyboard ?= "${AUTOREV}"
|
|
SRCREV:pn-matchbox-panel-2 ?= "${AUTOREV}"
|
|
SRCREV:pn-matchbox-themes-extra ?= "${AUTOREV}"
|
|
SRCREV:pn-matchbox-terminal ?= "${AUTOREV}"
|
|
SRCREV:pn-matchbox-wm ?= "${AUTOREV}"
|
|
SRCREV:pn-settings-daemon ?= "${AUTOREV}"
|
|
SRCREV:pn-screenshot ?= "${AUTOREV}"
|
|
. . .
|
|
|
|
These lines allow you to
|
|
experiment with building a distribution that tracks the latest
|
|
development source for numerous packages.
|
|
|
|
.. note::
|
|
|
|
The ``poky-bleeding`` distribution is not tested on a regular basis. Keep
|
|
this in mind if you use it.
|
|
|