On 03/16/2017 12:48 PM, Jack Mitchell wrote:
An issue with not having separate recipes is going to cause problems
with OTA package updates. I currently have a node package that I
maintain for a client and it's so big (excess of 30,000 files with all
deps) that we have to have a special update procedure of uninstalling
the package, re-installing the new version and then performing a system
update. A package update with 30,000 files on a quad core fast arm64
chip takes upwards of 40 minutes. It would be fantastic, if only the
core node application and changed dependencies could be updated.
Would it be possible to use something similar to the 'auto-package'
stuff we already have to split out the inner package dependencies and
have specific packages for each dependency but not a separate recipe?
Yes, certainly. In fact, I think npm.bbclass already does it.
Alex
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
