[New Feature]: Had a thought regarding portable applications and the `--System` Scope
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading the portable application installation and machine scope code in the WinGet CLI; the issue does not name specific files or tests. Determine how the install paths and directory permissions are handled, then assess whether junctions to the proposed ProgramData locations fit the existing behavior. Done means machine scope portable installs use the requested paths and resolve the write permission problem.
Written by the indexing model from the issue text.
Description
Description of the new feature/enhancement
When installing portable applications with machine scope that go in C:\Program Files\WinGet\ or C:\Program Files (x86)\WinGet\, instead of creating physical directories there:
Create 2 junction directories
From physical folder C:\ProgramData\WinGet\x64\
to Junction: C:\Program Files\WinGet\
and
From physical folder: C:\ProgramData\WinGet\x86\
to Junction: C:\Program Files (x86)\WinGet\
Proposed technical implementation details (optional)
Would solve permission issues since those folders have tighter permissions, an example of one that breaks: SDIO, it needs to write to its install folder. \Program files and \Program Files (x86) don't seem to like to let portable applications write to their install folders due to the restrictive nature of those parent directories.
At the moment I'm doing this myself using a post install script integrated into my custom ISO (for personal use). But I feel like this is a good enough work around for Winget to handle machine scope portable applications going forward.
- Dominant language
- C++
- Stars
- 26.6k
- Forks
- 1.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 41
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/winget-cli
-
Issue-Docs Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
microsoft/winget-cli#6692 ·
Maintainers usually reply within 2 days
-
Issue-Docs Possible-Duplicate
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/winget-cli#6493 · 1 comment ·
Maintainers usually reply within 2 days
-
Issue-Feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-cli#6427 ·
Maintainers usually reply within 2 days
-
Issue-Docs msstore
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
microsoft/winget-cli#6331 · 1 comment ·
Maintainers usually reply within 2 days
-
Command-Source Issue-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-cli#6148 ·
Maintainers usually reply within 2 days
All issues in microsoft/winget-cli
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
distante/esphome-components#50 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
feat
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Maintainers usually reply within 1 day