Feedback request on potential name change: i686 to w32devkit

Abierto
  • ¿Algo no está bien?
#81 1 comentario 4 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
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
c, cpp, fortran
Área
build-system, release

Línea de trabajo

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.

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

Descripción

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.zip unzips to w32devkit/
  • w32devkit-fortran-x.y.z.zip unzips to w32devkit/
  • w64devkit-x.y.z.zip unzips to w64devkit/
  • w64devkit-fortran-x.y.z.zip unzips to w64devkit/

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.

Lenguaje dominante
C
Estrellas
5k
Forks
408
Merge medio
4 h 40 min
PR fusionados (30 d)
2

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

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 skeeto/w64devkit

Todos los issues de skeeto/w64devkit

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.