[poky] do_deploy_archives for multiple images

[Ivan Efimov]

Hi Nicholas, 

Looks like you use different image recipes, doesn't you? 

You may use next folder path in "do_deploy_archives" to store tarballs to have uniq path per image: 
${DEPLOY_DIR}/archives/${IMAGE_NAME}/ 

Best regards, 
Ivan 


From: "Nicholas Clark" <nicholas.clark at gmail.com> 
To: "poky" <poky at yoctoproject.org> 
Sent: Monday, April 1, 2019 11:27:33 PM 
Subject: [poky] do_deploy_archives for multiple images 

I'm working on a design with a two different variants of a base image. One variant (a developer image) has some company-proprietary tools, and also some GPLv3 tools. The other variant (our production image) is fully license-compliant. 

In order to make sure that we're ready if/when we get GPL requests, I'd like to generate a releasable source tarball at build-time. Each image's do_deploy_archives task looks like it provides the right stuff, but they all go into the same shared directory (making it harder to separate them afterwards). 

Is there any way for me to set up image-specific archive directories, instead of having everything go to ${BUILD_DIR}/tmp/deploy/sources? 

-- 
_______________________________________________ 
poky mailing list 
poky at yoctoproject.org 
https://lists.yoctoproject.org/listinfo/poky 

-- 
[ https://inango.com/ |    ] 
Ivan Efimov 
Architect, Arch Group 
i.efimov at inango-systems.com 
T +7 343 298 0147 C +7 904 9 888 350 
[ https://inango.com/ | inango.com ] [ https://www.linkedin.com/company/inango ] 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/poky/attachments/20190404/64213968/attachment.html>