Prevent importing legacy unitypackage SDK in VCC/VPM SDK
Sayamame
Although the legacy SDK distribution has been stopped, many people still keep it.
Many people destroyed their VCC projects by importing the legacy SDK, based on their old knowledge from the legacy SDK.
(There are also several outdated articles that guide users to override import the SDK when trouble occurs, and the same is true for those who refer to those articles.)
To avoid such trouble, please prevent importing legacy unitypackage SDK in VCC/VPM SDK.
It may not be perfect, but it should be helpful.
As examples, lilToon and UnlitWF have a mechanism to prevent importing the unitypackage version if it has already been imported by UPM or VPM.
(Both are licensed under the MIT license.)
Log In
Sayamame
I forgot to link to the issue related to this problem.
Mikage_Kagetani
Is the scope of this issue you are talking about only affecting SDK 2?
Or does it also include SDK 3?
If SDK3 has already been imported, the protocol to remove it will run, so am I correct in my understanding that only SDK2 is affected?
Sayamame
Mikage_Kagetani: No.
This issue occurs with SDKs such as
VRCSDK3-AVATAR-2022.10.27.00.35_Public.unitypackage
. I expressed it as "legacy unitypackage SDK".SDK2 was left out of the assumption. (Of course, it would be better to prevent this as well.)
If you import the VPM SDK when the legacy SDK has already been imported, the old SDK will be properly removed by the VPM mechanism.
However, what we want to talk about here is when the legacy SDK is imported when the VPM SDK has already been imported.
Mikage_Kagetani
Sayamame:
I understand.
Perhaps you could also try to combine the issues mentioned here.
Also, if you are in a hurry, why not raise the ticket over here?
Sayamame
Mikage_Kagetani: No, that Canny is not related.
What you are assuming is probably the opposite of what I am assuming.
The VPM mechanism is working correctly for the VPM SDK.
I am already aware of the bug mentioned in that Canny, but it should not be related to this Canny.
Because legacyFolders and legacyFiles are supposed to work when importing the VPM SDK into an environment where the legacy sdk has already been imported.
As mentioned before, we want to talk about the case of accidentally importing the legacy SDK into an environment where the VPM SDK has already been imported.