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
Scoop reverts to creating and using a config.json file in the %USERPROFILE%\.config\scoop folder, regardless of whether a config.json file exists within the scoop installation dir (i.e., %USERPROFILE%\scoop\config.json).
Relates to Feature Request 4498 and its implementation in 5369.
Expected Behavior
If there is a config.json file in the scoop installation folder (e.g., %USERPROFILE%\scoop), scoop should defer to that file. It should not still create a .config folder, a config.json file within it, or ignore the config.json in the scoop root folder. (Additionally, scoop should not recreate the external folder and file if deleted in deference to using a local portable config file—even if scoop is not installed on portable media.)
Additional context/output
I created a config.json in the scoop root dir (C:\Users\%USERNAME%\scoop\) and renamed the folder the original %USERPROFILE%\.config folder to hide it. I wanted to test if a local config file in the root folder would actually work. As soon as I invoked scoop in the terminal again, though, it recreated .config\scoop\config.json. Ticket 5369 gives the following instructions:
. . . Is there something more required to make scoop recognize the local scoop\config.json? Is %USERPROFILE%\scoop\ the wrong place in the "root directory" for the config.json file?
Possible Solution
N/A
System details
Windows version: 10
OS architecture: 64bit
PowerShell version: v7.4.0-preview.4
Additional software: Git, curl, aria2, etc. installed with scoop.
Bug Report
Current Behavior
Scoop reverts to creating and using a
config.json
file in the%USERPROFILE%\.config\scoop
folder, regardless of whether a config.json file exists within the scoop installation dir (i.e.,%USERPROFILE%\scoop\config.json
).Relates to Feature Request 4498 and its implementation in 5369.
Expected Behavior
If there is a
config.json
file in the scoop installation folder (e.g.,%USERPROFILE%\scoop
), scoop should defer to that file. It should not still create a.config
folder, aconfig.json
file within it, or ignore theconfig.json
in the scoop root folder. (Additionally, scoop should not recreate the external folder and file if deleted in deference to using a local portable config file—even if scoop is not installed on portable media.)Additional context/output
I created a
config.json
in the scoop root dir (C:\Users\%USERNAME%\scoop\
) and renamed the folder the original%USERPROFILE%\.config
folder to hide it. I wanted to test if a local config file in the root folder would actually work. As soon as I invokedscoop
in the terminal again, though, it recreated.config\scoop\config.json
. Ticket 5369 gives the following instructions:. . . Is there something more required to make scoop recognize the local
scoop\config.json
? Is%USERPROFILE%\scoop\
the wrong place in the "root directory" for theconfig.json
file?Possible Solution
N/A
System details
Windows version: 10
OS architecture: 64bit
PowerShell version: v7.4.0-preview.4
Additional software: Git, curl, aria2, etc. installed with scoop.
Scoop Configuration
%USERPROFILE%\scoop\config.json
:%USERPROFILE%\.config\scoop\config.json
:The text was updated successfully, but these errors were encountered: