Bazel installer should not overwrite ~/.bazelrc

[philwo]

The Bazel installer currently moves ~/.bazelrc to ~/.bazelrc.bak and creates an empty file instead, which is rather annoying. We should change the installer to not touch the file.

[ittaiz]

You mean that having a ~/.bazelrc is no longer mandatory so the installer shouldn't try to create one?

…

On Sat, 6 May 2017 at 10:29 Philipp Wollermann ***@***.***> wrote: The Bazel installer currently moves ~/.bazelrc to ~/.bazelrc.bak and creates an empty file instead, which is rather annoying. We should change the installer to not touch the file as that mechanism is no longer needed. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2958>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABUIF0cdPZ5QOWcjcBL7paMGWpth2imdks5r3CFmgaJpZM4NSqOC> .

[philwo]

@ittaiz I don't think a ~/.bazelrc was ever mandatory, Bazel should work just fine without any configuration files like /etc/bazelrc or ~/.bazelrc. :)

The installer currently always wants to create an empty ~/.bazelrc file. If the user has already created a ~/.bazelrc file (and possibly put some config flags there), it will be moved to ~/.bazelrc.bak, which is annoying, because your next step is probably to just move it back to ~/.bazelrc.

Instead the installer should just not touch the file at all - if it doesn't exist already, don't create one. If one exists, leave it as is.

[softprops]

On May 6, 2017 4:37 PM, "Philipp Wollermann" <notifications@github.com> wrote: @ittaiz <https://github.com/ittaiz> I don't think a ~/.bazelrc was ever mandatory, Bazel should work just fine without any configuration files like /etc/bazelrc or ~/.bazelrc. :) The installer currently always wants to create an empty ~/.bazelrc file. If the user has already created one (and possibly put some config flags there), it will be moved to ~/.bazelrc.bak, which is annoying, because you basically have to immediately move it back. Instead it should just not touch the file at all - if it doesn't exist already, don't create one. If one exists, leave it as is. +1 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2958 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAIwlomGv_P6P-fhkfrcd_9sfkesGVYks5r3NoKgaJpZM4NSqOC> .

[ittaiz]

Ok. I just don't understand what you meant by "that mechanism is no longer needed" but I guess it's not that important.

…

On Sun, 7 May 2017 at 0:04 doug tangren ***@***.***> wrote: On May 6, 2017 4:37 PM, "Philipp Wollermann" ***@***.***> wrote: @ittaiz <https://github.com/ittaiz> I don't think a ~/.bazelrc was ever mandatory, Bazel should work just fine without any configuration files like /etc/bazelrc or ~/.bazelrc. :) The installer currently always wants to create an empty ~/.bazelrc file. If the user has already created one (and possibly put some config flags there), it will be moved to ~/.bazelrc.bak, which is annoying, because you basically have to immediately move it back. Instead it should just not touch the file at all - if it doesn't exist already, don't create one. If one exists, leave it as is. +1 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2958 (comment)>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AAAIwlomGv_P6P-fhkfrcd_9sfkesGVYks5r3NoKgaJpZM4NSqOC > . — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2958 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABUIF5bMaAvWmwGSuY78O4Vytc1IxsiZks5r3OBGgaJpZM4NSqOC> .

[philwo]

@ittaiz No problem and sorry for the misunderstanding. With "that mechanism", I just meant "the part of the installer that deals with the ~/.bazelrc", but re-reading my issue description I can see now how that might be confusing. I removed the part of the sentence.