You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For vrchat-curated packages, the vpm migration will migrate legacy packages to vpm maintained packages.
It might be useful to migrate non-vrchat-curated packages to vpm installation.
Purpose / 目的
We can easily migrate liltoon or some other tools / shaders easily
Additional context / 補足
No response
The text was updated successfully, but these errors were encountered:
Shouldn't this be defined within the legacyFolder option of the VPM spec ?
Or are you implying to "manually" add those packages on the migrated project to replace the old packages ?
The VCC and ALCOM will migrate an unitypackage-based package to vpm package by checking legacy folders.
If legacyFolders of an package are found, VCC will install the package and (as if we installed manually) VCC will remove the unitypackage-based package by removing legacy folders.
The legacyFolders should point the folder contains package only so the migration should be safe.
Shouldn't this be defined within the legacyFolder option of the VPM spec ?
Do you mean it should be optional to use specific legacyFolders entry to be used in auto migration or not?
Or are you implying to "manually" add those packages on the migrated project to replace the old packages ?
No, removing legacy unitypackage-based package on manual installation is already implement as legacyFolders and legacyFiles.
Summary / 概要
For vrchat-curated packages, the vpm migration will migrate legacy packages to vpm maintained packages.
It might be useful to migrate non-vrchat-curated packages to vpm installation.
Purpose / 目的
We can easily migrate liltoon or some other tools / shaders easily
Additional context / 補足
No response
The text was updated successfully, but these errors were encountered: