Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Deprecate the snap build

Abierto
  • ¿Algo no está bien?
#973 17 comentarios 3 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
go, shell
Área
build-system, cli, release

Línea de trabajo

No se nombran archivos ni pruebas. Revisa el snap build actual y el flujo de instalación en Linux; después, aclara si el alcance previsto es la eliminación, un instalador de reemplazo o ambos. Los maintainers deben definir cuándo se considera completado, incluida la ruta de instalación compatible y cualquier instrucción necesaria para los usuarios.

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

Descripción

With quite some regularity there are issues reported with the snap build.

  • It prints instructions to use the opaque and absolute snap path to binary to execute commands. One should never run those directly
  • It creates config within the sandbox but searches for them in the user dir when trying to read them
  • It It sometimes doesn't seem to have permissions to create the users config in ~/.config

And there have been other weird things reported in the gitter where the student didn't create a bug report here.

No one of the maintainers of the CLI seems able to reproduce the issues, even when using snap on their own.

Therefore my conclusion of this issue is, that the snap-sandbox is also a blackbox for us that introduces unsolvable problems. Since the introduction of the snap, requests for help with installation problems have massively increased in gitter instead of getting less.

The majority of issues are because of snap weirdnesses, and solved by removing the snap replacing it by a manual installation.
Second is beeing confused about the unpack location in a manual installation.
Third is not having installed snap properly before trying to use it to install exercism

(This ranking is based on my personal perceiption and only includes linux derivations)

And even though I still do not like the idea of having a not-managed-by-the-package-manager-program on the computer, I realy think, that creating a simple shell script, which downloads the binary for the current platform, moves it to ~/bin and prints a message that one has to add export PATH=~/bin:"$PATH" to the ~/.bashrc or ~/.zshrc respectively or equivalent commands to equivalent files in any other shell would be the best thing to do.

Students then could install by a curl https://exercism.io/get-exercism | sh or similar.

Lenguaje dominante
Go
Estrellas
1.4k
Forks
363
Merge medio
24 min
PR fusionados (30 d)
1

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 exercism/cli

Todos los issues de exercism/cli

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.