I had filed bug 1257478 specifically for tackling the git configuration issue and when this larger plan was brought up, my inclination to work on it diminished :) If this broader work is not prioritized, could we split it into smaller bugs so that it's manageable in weekend-sized chunks? I realize there will be some temporary churn (e.g. a not very long-lived 'mach git-setup'), but we could get at the final goal faster.
Panos On Tue, May 16, 2017 at 3:38 AM, Gregory Szorc <g...@mozilla.com> wrote: > I thought there was a bug on file, but maybe not. I've long thought the > following changes should be made: > > * `mach mercurial-setup` should be rolled into `mach bootstrap` > * `mach doctor` should be rolled into `mach bootstrap` > * `mach bootstrap` should remember answers from last time and not prompt on > subsequent runs unless a flag is specified > * `mach bootstrap` should be renamed/aliased to `mach refresh` (or similar) > to reflect that it is no longer limited to initial system setup > > And of course there are missing features, such as Git configuration and > offering to create a Git clone. > > bootstrap, doctor, and mercurial-setup are all under-loved features. They > tend to not get prioritized very highly. Typically, new features or bug > fixes are implemented when someone feels like scratching an itch. I wish I > could justify spending more time on these things because turnkey optimal > development environments are important. But it's a lot of ongoing work and > there always seems to be something else competing for my time :( > > On Mon, May 15, 2017 at 4:59 PM, Ralph Giles <gi...@mozilla.com> wrote: > > > The stand-alone bootstrap.py script actually has a --no-interactive > > option (which answers 'yes' to everything) but the mach wrapper > > doesn't support this. > > > > `mach mercurial-setup` takes an --update-only option. Maybe we > > implementing something like that for `mach boostrap` would help. Or > > calling it something more descriptive like `mach update-deps`. Like > > mercurial-setup, it could still use the bootstrap python module to > > install things. While the two use cases are different, it makes sense > > to share code between an initial development environment setup script > > and one that updates that environment. > > > > -r > > > > On Mon, May 15, 2017 at 3:39 PM, Ethan Glasser-Camp > > <eglasserc...@mozilla.com> wrote: > > > Actually, I think my real question is "What is the intended way for > > > developers to keep their development environment up-to-date?" I don't > > think > > > that way should require a developer to answer questions, because the > > > answers presumably haven't changed since the last time they answered > > them. > > > If the intended way is `mach bootstrap`, then I think `mach bootstrap` > > > should have an option to skip the questions[*]. If `mach bootstrap` is > > only > > > intended to run once when setting up a new development environment, > then > > > maybe there should be a `mach tune-up` command or something like that. > > > > > > I'm happy to file bugs for whichever is the case, but I'm not sure > which > > > one it is. > > > > > > Ethan > > > > > > [*] When using `./mach bootstrap --settings ./mozconfig`, I get: `The > > > bootstrap command does not accept the arguments: --settings > ./mozconfig`. > > > When using `./mach --settings ./mozconfig bootstrap`, I get the > > questions. > > > > > > > > > On Fri, May 12, 2017 at 1:04 PM, Geoffrey Brown <gbr...@mozilla.com> > > wrote: > > > > > >> I'm not sure. I always just answer the prompts and am happy with that. > > >> > > >> There is a --settings option, which sounds like it might be helpful, > > but I > > >> don't have any experience with that. > > >> > > >> - Geoff > > >> > > >> On Fri, May 12, 2017 at 9:00 AM, Ethan Glasser-Camp < > > >> eglasserc...@mozilla.com> wrote: > > >> > > >>> Is there a way to run it without having to reanswer the configuration > > >>> questions? > > >>> > > >>> Ethan > > >>> > > >>> > > >> > > > _______________________________________________ > > > dev-platform mailing list > > > dev-platform@lists.mozilla.org > > > https://lists.mozilla.org/listinfo/dev-platform > > _______________________________________________ > > dev-platform mailing list > > dev-platform@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-platform > > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
