[New Feature]: Had a thought regarding portable applications and the `--System` Scope

Open
#6,667 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
cli

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

Issue-Feature
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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/winget-cli

All issues in microsoft/winget-cli

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.