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

Better setup experience for third-party packagers?

Abierto
  • ¿Algo no está bien?
#5,149 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
rust
Área
cli, release

Línea de trabajo

The issue is a design question, not a ready task: rustup-init copies itself to rustup instead of linking, which blocks packagers from updating one installation. Read the linked Fedora discussion and issue #4754 to see the packager constraints, then check how the installer creates the rustup binary. Done means maintainers agree on an approach, such as an opt-in link, before any code is written.

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

Descripción

enhancement

So, given that rustup-init and rustup are "the same", I guess you could argue I do have two installations. The problem is that both originate from what should be a single installation, and updating one (rustup-init) doesn't update the other (rustup). There's further discussion on Ask Fedora now: discussion.fedoraproject.org/t/what-is-the-correct-way-to-keep-rustup-up-to-date/204625

Many thanks for the follow-up. In that case, no wonder why other package managers who have disabled auto-update all skipped the installer phase so that they can keep rustup itself up-to-date...
Maybe in that case we should link rather than copy the binary?
https://github.com/Rust-GPU/rust-gpu/issues/669#issuecomment-6207311500

Currently, third-party packagers are in a dilemma when they disable auto-update (which is a reasonable choice on their side):

  • Either they should package rustup-init and use the original installer flow, at the cost of not being able to update rustup regularly, because rustup-init copies (rather than links) itself to rustup.
  • Or they should package rustup-init while renaming them to rustup which addresses the upgrade problem at the cost of bypassing a whole bunch of notes etc. that we have put in the setup flow.

This is a common source of confusion in third-party installations, such as in #4754.

Maybe there is a way to make everyone happier in this case. My preference would be making rustup-init easier to setup, possibly by an opt-in linking rather than copying, so that we can keep the original flow. Not sure if that is entirely feasible though, to be investigated.

Lenguaje dominante
Rust
Estrellas
7.1k
Forks
1.1k
Merge medio
1 d 11 h
PR fusionados (30 d)
39

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 rust-lang/rustup

Todos los issues de rust-lang/rustup

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.