Hi Ross,
>
>
>> On 23 Jun 2026, at 00:03, John Ripple via lists.openembedded.org
>> <john.ripple=keysight.com@...> wrote:
>>
>> The go-vendor class has a hardcoded destsuffix variable used to unpack
>> sources fetched with the go_src_uri function. This was causing a conflict
>> with insane.bbclass which prohibts setting S = "${UNPACKDIR}/git" which
>> was needed to find the vendored sources in the hardcoded location.
>> Changing this unpack location to use the standard base package name (BP)
>> fixes the previous issue and no longer requires manually setting S in the
>> recipes that use go-vendor.
>
> Thanks for these patches. Sadly we don’t have a test case for the
> go-vendor class, as you clearly use it would you be able to write a small
> test case to verify that a recipe using the go-vendor class works? We can
> host little test repositories on git.yoctoproject.org if needed (for
> example, https://git.yoctoproject.org/recipetool-go-test/ ).
>
Is there anything the test should do in particular or is there a general guides
for what should be tested for a bbclass? I'm not very familiar with the Yocto
self test framework so any tips or documentation would be appreciated. I'll try
to follow what the gotoolchain.py test does if nothing else.
John
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#239655):
https://lists.openembedded.org/g/openembedded-core/message/239655
Mute This Topic: https://lists.openembedded.org/mt/119933336/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
