Am Mi., 27. Feb. 2019 um 06:28 Uhr schrieb Nathan Froyd <nfr...@mozilla.com>:
> > > If people have problems with bootstrap (it doesn't do enough, it > > > assumes too much about your system, etc. etc.), please file bugs on > > > what's wrong. We need to start depending more on bootstrap for > > > everything, to the point of "you can't depend on X unless it gets > > > installed via bootstrap", and we can't get to that world if we don't > > > know what rough edges people find in bootstrap. > > > > Do you have a suggestion on how to do that in practice? Rolling back > > from a broken development environment is easily a couple of hours of > > work, in the case of homebrew breaking all my virtualenvs, for example. > > It's not clear to me what bootstrap does that breaks things. Do you > want the ability to skip installing everything via homebrew? Note that it is already possible to skip all changes that touch the system package manager by doing `mach bootstrap --no-system-changes`. This won't install everything that is required to build, but it should at least install the stuff that is available as pre-built toolchains from CI (including clang, node, cbindgen, etc). I suspect (but don't know), that most (all?) recent changes to mach bootstrap fall under this grouping. Perhaps making it possible to force `mach bootstrap --no-system-changes` after a key change would be reasonable and solve a sufficient subset of the problem for now? It would still have the re-download issue that dmajor pointed out, although I suppose that bug could be made to block the option to force. Dan _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
