Description:
The SDCC installer for Windows overwrites the entire system PATH variable instead of appending to it.
Steps to Reproduce:
1. Check current PATH (echo %PATH% > before.txt).
2. Run SDCC installer version 4.2.0 by winget install sdcc
3. After installation, check PATH again (echo %PATH% > after.txt).
4. Observe that previous PATH entries are gone.
Expected behavior:
The installer should append SDCC's path to the existing PATH.
Actual behavior:
The installer overwrites the entire PATH, deleting all previous entries.
System:
Windows 10, SDCC 4.2.0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Description:
The SDCC installer for Windows overwrites the entire system PATH variable instead of appending to it.
Steps to Reproduce:
1. Check current PATH (echo %PATH% > before.txt).
2. Run SDCC installer version 4.2.0 by
winget install sdcc3. After installation, check PATH again (echo %PATH% > after.txt).
4. Observe that previous PATH entries are gone.
Expected behavior:
The installer should append SDCC's path to the existing PATH.
Actual behavior:
The installer overwrites the entire PATH, deleting all previous entries.
System:
Windows 10, SDCC 4.2.0
Suggests update winget installation version to 4.5.0.
As far as I know, nobody here has been involved in the creation of winget manifests for SDCC.
I found this, though: https://github.com/microsoft/winget-pkgs/issues/99198