gsf is a package manager, and it does not allow you to delete files that are no longer in the template. And simple structure imply that gsf does not know the previous version of gear, and gsf cannot recreate the structure to compare it with the state in the repository. But perhaps it can be stored practically “for free.” If this is possible, we can discuss this solution and implement it.
We need to analyze whether it is possible to simply store the previous state (gear version) in text format for git.
To Reproduce
Gear v1 with:
Gear v2 with:
- file1 (file2 has been deleted)
gsf install gear_v1 ..., and after this gsf install gear_v2 ...
Version
v0.6.5
Logs
not required
Additional information
No response
gsf is a package manager, and it does not allow you to delete files that are no longer in the template. And simple structure imply that gsf does not know the previous version of gear, and gsf cannot recreate the structure to compare it with the state in the repository. But perhaps it can be stored practically “for free.” If this is possible, we can discuss this solution and implement it.
We need to analyze whether it is possible to simply store the previous state (gear version) in text format for git.
To Reproduce
Gear v1 with:
Gear v2 with:
gsf install gear_v1 ..., and after thisgsf install gear_v2 ...Version
v0.6.5
Logs
not required
Additional information
No response