Feedback request on potential name change: i686 to w32devkit
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 25/100
- issue の種類
- 機能追加
- 明瞭さ
- 説明が足りない
- 活発さ
- 停滞
- 領域
- build-system, release
調査の方向性
Start with the current GitHub Releases presentation and README.md, then compare the proposed w32devkit artifact names and directory layout with the existing release assets. Done means an agreed naming and packaging decision, with any resulting release navigation or README changes explicitly defined.
索引モデルが issue の本文から書いたものです。
説明
I'm considering renaming the "i686" variant to "w32devkit". On my systems I keep both 64-bit and 32-bit toolchains side-by-side and I rename the latter locally in order to tell them apart. For releases I'd rename both the zip and the top-level directory. I'm also dropping the "mini" variants since the difference has become so little. That makes for these four build artifacts:
w32devkit-x.y.z.zipunzips tow32devkit/w32devkit-fortran-x.y.z.zipunzips tow32devkit/w64devkit-x.y.z.zipunzips tow64devkit/w64devkit-fortran-x.y.z.zipunzips tow64devkit/
I like that the names are simpler and more concise, and that I can unzip 32-bit and 64-bit versions side-by-side without intervention. The 64-bit builds are unchanged, so no disruption there.
My concern is that some people, especially newcomers, have trouble navigating (and even finding!) GitHub's "Releases" page. The default and least specialized build is w64devkit-x.y.z.zip, and by sheer luck, it currently sorts to the top, ignoring source.tar. However, with the rename it will be 5th in the list, counting .sigs, which is a less obvious download. Though perhaps I could kill two birds with one stone by putting download links in README.md — or get around to finally building a simple, official website where I control navigation.
I've long wished it was possible to blend releases, by, say, unzipping one atop the other, or putting both in PATH. The buried toolchain would be accessible by its architecture triple (e.g. i686-w32-mingw32-gcc). Renaming the 32-bit toolchain would make merging an installation more difficult. However, even in the relatively simple PATH case, the buried toolchain is confused about which tools to use, and I haven't yet figured out how to fix it.
(Side note: I've also considered not building Fortran releases — while still maintaining the variant patch — but there are a substantial number of users, notably the llama.cpp community, so it's worth continuing.)
Feedback welcome.
- 主要言語
- C
- スター
- 5k
- フォーク
- 408
- 平均マージ
- 4時間 40分
- マージ済み PR（30日）
- 2
環境構築
- Dockerfile または Docker Compose ファイルあり
- プルリクエストのテンプレートなし
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
skeeto/w64devkit のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
-
難易度 4/5 3〜5日 初心者へのやさしさ 46/100
-
難易度 3/5 1〜2日 初心者へのやさしさ 52/100
-
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
-
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
skeeto/w64devkit の issue をすべて見る
似ている issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
msys2/MINGW-packages#33356 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
kmod-project/kmod#492 ·
メンテナーはふだん 4 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
PecanProject/sipnet#435 · コメント 1 件 ·
メンテナーはふだん 2 日以内に返信
-
SDL_GPU Vulkan: wrong screen orientation on OpenHarmony (preTransform set without pre-rotation)オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
libsdl-org/SDL#16670 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100