Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Faster bootstrap runs without changing what a profile installs

Aperta
  • Qualcosa non va?
#60 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
docker, shell
Ambito
build-system

Direzione di ricerca

Start by reading build/tart/vm run and install/brew, which the issue names as the VM launch and brew installation entry points. Check how profile sets are selected and how the checkout is mounted, then trace the bootstrap loop for mise, runtimes, and nix. Done means the allowed brew sets install in one bundle call, the host cache is reused, and a fresh run still proves the complete profile works.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

A full headless run spends most of its time in the brew step. Almost all of that time goes to downloading bottles. The previous run already downloaded the same bottles into a VM that was then thrown away.

The profile cut is right and should not be trimmed further. The laptop needs gcc, llvm, pandoc, and tectonic, so the VM must install them too. The time can be recovered elsewhere.

  1. Share Homebrew's download cache from the host. build/tart/vm run already mounts the checkout. A second mount, read-write, can hold the cache. HOMEBREW_CACHE inside the guest points at it. Bottles then download once per host instead of once per VM, and a reset VM pours from cache. This is the biggest win, and it changes nothing about the result.

  2. One bundle call per run. install/brew bundles set by set so that a profile can omit some sets. Bundle fetches every download for one call in parallel. Twelve calls therefore mean twelve serial fetch phases. The installer can generate a temporary Brewfile that includes only the allowed sets and run one brew bundle against it. The per-set omission survives, and the run gets one fetch phase.

  3. Homebrew environment for the run. The bootstrap can set HOMEBREW_NO_AUTO_UPDATE, HOMEBREW_NO_INSTALL_CLEANUP, and HOMEBREW_NO_ENV_HINTS for its own process. Those three stop the repeated update checks, the cleanup passes between calls, and the hint noise in the log. The installer still runs brew update once, explicitly.

  4. A checkpoint VM for the loop, never for the proof. tart clone of a VM stopped right after the brew step gives a starting point for iterating on mise, runtimes, and nix in minutes. The fresh run stays the only evidence that the whole thing works. This checkpoint would have shortened the last four iterations considerably.

Lingua principale
Shell
Stelle
1
Fork
0
Merge medio
11m
PR unite (30g)
2

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di indexzero/dotfiles

Tutte le issue di indexzero/dotfiles

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.