Re: [docs] [yocto-docs][PATCH v2 2/2] migration-5.2: add virtual provider change

["Antonin Godard" <antonin.godard@bootlin.com>]

Hi Quentin,

On Thu Feb 6, 2025 at 10:25 AM CET, Quentin Schulz wrote:
[...]
>>> +
>>> +PREFERRED_PROVIDER_virtual/nativesdk-cross-cc = "gcc-crosssdk-${SDK_SYS}"
>>> +PREFERRED_PROVIDER_virtual/nativesdk-cross-c++ = "gcc-crosssdk-${SDK_SYS}"
>>> +PREFERRED_PROVIDER_virtual/nativesdk-compilerlibs = "nativesdk-gcc-runtime"
>>>
>>> Now looking a bit more into the changes made in this commit, there isn't
>>> a simple search and replace that can be used, sometimes it's replacing a
>>> variable with one value, sometimes with another. Depends on the recipe
>>> the change is made in I guess?
>> 
>> I guess so. It's probably going to be different based on the recipe, but I
>> wouldn't know how to phrase it here. I just gave some more examples to
>> illustrate the changes. Any idea on a better way to explain this?
>> 
>
> The issue is that the example implies that the change is simple and 
> automatic, it is not I'm afraid. For the variables that we know can be 
> changed automatically then it's fine, I believe that's the case for 
> PREFERRED_PROVIDER with TARGET_PREFIX. For the others, maybe stating 
> that one replacement could be X -> Y but it depends, so rather see <link 
> to commit> to check for yourself.
>
> Don't have a better suggestion than that unfortunately.

I get what you mean, thanks. I think I will rephrase this is bit, stating that
those are examples, but should not be taken as a simple grep & replace. I'll
also link to the commit in question.

Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com