067b37abdc
StarlingX has many repos to maintain meta data (patches and config files) for packages, previously we added a local copy of those files as bitbake's metadata for each recipe which may cause maintenance issue. So add a method to avoid that, which includes: * Add new recipes stx-${STX_REPO}-source for thoes stx git repo and put them into the work-shared directory so they can be used by other recipes that need the stx meta data, so it will reduce downloads and increase re-use. * Add stx-source.bbclass for easily creating the work-shared recipes * Add stx-metadata.bbclass for those recipes that need the stx meta data, it will add dependency on the stx-${STX_REPO}-source and redefine the SRC_URI before do_patch, so it can find the patches in stx repo in work-shard and do the patch, and other meta data like config files can be used in do_install, then the local copy of those meta data can be removed, and for the future upgrade, we don't need to manually check and update those meta data any more. Story: 2008952 Task: 42576 Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Change-Id: I0d07f2f6002eb0cee97ae86f95571d340de08a0b |
||
---|---|---|
.. | ||
conf | ||
stx-ansible-playbooks | ||
stx-config | ||
stx-config-files | ||
stx-distributedcloud | ||
stx-fault | ||
stx-gui | ||
stx-ha | ||
stx-integ | ||
stx-integ-kubernetes | ||
stx-metal | ||
stx-monitor-armada-app | ||
stx-monitoring | ||
stx-nfv | ||
stx-openstack-armada-app | ||
stx-platform-armada-app | ||
stx-update | ||
stx-upstream | ||
stx-utilities |