summaryrefslogtreecommitdiff
path: root/meta/recipes-connectivity/zeroconf
diff options
context:
space:
mode:
authorLianhao Lu <lianhao.lu@intel.com>2011-12-22 15:29:11 +0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-01-11 10:33:24 +0000
commit9979107d8eaf503efd921564385859b1e83dbb3c (patch)
treea79dd735499d19f0b5ebefc96ccb79c001d50d6b /meta/recipes-connectivity/zeroconf
parent0df0399677a6677fc810e32e9275ee9e79021e9a (diff)
downloadopenembedded-core-9979107d8eaf503efd921564385859b1e83dbb3c.tar.gz
openembedded-core-9979107d8eaf503efd921564385859b1e83dbb3c.tar.bz2
openembedded-core-9979107d8eaf503efd921564385859b1e83dbb3c.tar.xz
openembedded-core-9979107d8eaf503efd921564385859b1e83dbb3c.zip
meta/PRService: Added export/import fuctions.
[YOCTO #1556] - Modified meta/class/package.bbclass and prserv.bbclass according to the change in PR service by adding PACKAGE_ARCH into the query tuple. - Added prexport.bbclass, primport.bbclass to export/import AUTOPR values from/to PRService. - Move PR service related common code to lib/oe/prservice.py. - Supported reading the AUTOPR values from the exported .inc file instead of reading it from remote PR service. - Created a new script bitbake-prserv-tool to export/import the AUTOPR values from/to the PR service. Typical usage scenario of the export/import is: 1. bitbake-prserv-tool export <file> to export the AUTOPR values from the current PR service into an exported .inc file. 2. Others may use that exported .inc file(to be included in the local.conf) to lockdown and reproduce the same AUTOPR when generating package feeds. 3. Others may "bitbake-prserv-tool import <file>" to import the AUTOPR values into their own PR service and the AUTOPR values will be incremented from there. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
Diffstat (limited to 'meta/recipes-connectivity/zeroconf')
0 files changed, 0 insertions, 0 deletions