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

Abierto
#6,667 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp
Área
cli

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
C++
Estrellas
26.6k
Forks
1.8k
Merge medio
3 d 10 h
PR fusionados (30 d)
41

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/winget-cli

Todos los issues de microsoft/winget-cli

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.