diff options
| author | Darren Hart <dvhart@linux.intel.com> | 2014-03-25 14:04:21 -0700 |
|---|---|---|
| committer | Darren Hart <dvhart@linux.intel.com> | 2014-03-25 14:04:21 -0700 |
| commit | a1491bc54b60a1c622a9060756fd9b145bc01378 (patch) | |
| tree | 9d902aa8fdb3fcc121e076c2dcebbc0fe7e7702f /meta-chiefriver/README.sources | |
| parent | f122b5a10114416c55d015305fdd011d86e71353 (diff) | |
| download | meta-intel-a1491bc54b60a1c622a9060756fd9b145bc01378.tar.gz | |
linux-yocto-dev: Specify SRC_REVs for intel-core* machines
The automatic SRCREV AUTOREV anonymous python in linux-yocto-dev.bb
will only trigger on the PREFERRED_PROVIDER_virtual/kernel being
linux-yocto-dev if it is set in local.conf, or a similar file parsed
prior to itself.
Since these two machines currently specify linux-yocto-dev in the
machine configuration, the AUTOREV doesn't trigger - and we do not want
AUTOREV specified in the recipe itself to avoid breakage in the event
of no network access.
This is a bizarre little corner case as machines typically do not
specify linux-yocto-dev. For the time being, fix the do_fetch failure by
specifying SRCREVs for the two intel-core* machines. Users who want
AUTOREV can specify THAT in their local.conf. This way it doesn't break
out of the box.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Diffstat (limited to 'meta-chiefriver/README.sources')
0 files changed, 0 insertions, 0 deletions