the default HOSTTOOLS configuration (poky/meta/conf/bitbake.conf) contains 'git', but not 'git-lfs'; as such any calls to "git lfs ..." result in a failure - even when it is available on the host! imho, 'git-lfs' should be included in the default HOSTTOOLS, at least when 'largefile' is given in DISTRO_FEATURES. -- or how else should developers "enable" git-lfs if they need to? possible resolutions: a) poky/meta/conf/bitbake.conf: add "git-lfs" to HOSTTOOLS_NONFATAL - in case it's not installed on the host b) poky/meta/conf/layer.conf: add HOSTTOOLS_NONFATAL += "${@bb.utils.contains('DISTRO_FEATURES', 'largefile', 'git-lfs', '', d)}" --- if that is all wrong, I'd appreciate a link to any documentation describing how to get access to git-lfs within a recipe!
We don't require users to install git-lfs and as such it wouldn't be in HOSTTOOLS. If you need it, I'd expect there to be a git-lfs-native recipe which you could add to DEPENDS which would then make it available. You can obviously work around this by adding to HOSTTOOLS locally but I don't think the project will do that by default. Also, the largefile DISTRO_FEATURE is something totally different to git-lfs.
well, we moved from Yocto-2.0 where no HOSTTOOLS was and all host-tools were directly accessible inside any recipe. not having the same behavior seemed to be a bug..
...and it's even worse: when one does a "bitbake -c devshell" to find out why a git-lfs wouldn't work inside his recipe, he only finds out that git-lfs DOES WORK in the devshell, he'll be confused.