Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Set no_junction per application #6087

Open
nicerloop opened this issue Jul 31, 2024 · 0 comments
Open

[Feature] Set no_junction per application #6087

nicerloop opened this issue Jul 31, 2024 · 0 comments

Comments

@nicerloop
Copy link

nicerloop commented Jul 31, 2024

Feature Request

Is your feature request related to a problem? Please describe.

I want to be able to update pwsh with scoop run from pwsh
This requires no_junction to be enabled during install or update (due to some recursive path problems in setting up the shim).
But I do not want to change the default behaviour for all other applications.

Describe the solution you'd like

I would like an install-time flag that would be persisted in install.json and used whenever any operation handles the application (update, status, reset ...).

scoop install --no-junction main/pwsh

Given sufficient guidance, I could try an implement this feature if it is deemed valuable in scoop

Describe alternatives you've considered

My current workaround is to install pwsh with no_junction enabled, hold it, and disable no_junction.

scoop config no_junction true
scoop install pwsh
scoop hold pwsh
scoop config no_junction true

Then to perform the update, I re-enable no_junction, unhold pwsh, update pwsh, and re-disable no_junction

scoop config no_junction true
scoop config ignore_running_processes true
scoop unhold pwsh
scoop update pwsh
scoop hold pwsh
scoop config no_junction false
scoop config ignore_running_processes false
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant