Deprecate the snap build
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 领域
- build-system, cli, release
调研方向
未指定文件或测试。请检查当前的 snap build 和 Linux 安装流程，然后明确预期范围是弃用、替代安装程序，还是两者兼有。完成标准应由维护者定义，包括受支持的安装路径以及任何面向用户的必要说明。
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- Go
- 星标
- 1.4k
- 派生
- 363
- 平均合并
- 24 分钟
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
exercism/cli 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
-
难度 5/5 一周以上 新手友好度 35/100
-
难度 2/5 1-3 小时 新手友好度 38/100
-
难度 4/5 3-5 天 新手友好度 35/100
-
难度 4/5 3-5 天 新手友好度 25/100
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 88/100
-
phase:v3 type:harness
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
war-and-code/dircue#200 ·
维护者通常 1 天内回复
-
actor/human kind/bug priority/important-soon triage-accepted
难度 2/5 1-3 小时 新手友好度 66/100
kelos-dev/kelos#1804 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复