Handle etc files more nicely #15751
Comments
This is ideal, since the user gets revision control over their configuration files. Which is something nobody else is doing, and it would certainly help with package management for the user.
Would be pretty sweet. |
Etckeeper does this for apt on Ubuntu |
Yep, I've used |
User edits
Months later:
And there we have it. The merge either succeeds or requires the user to do some git. We can have a |
Looks good to me. |
The place for the code to go is in If we all very lucky I will do it this weekend. But that bugs in |
Because of the way we install etc files to 'HOMEBREW_PREFIX/etc` 3. and 4. will be too hard. |
Closing in favour of #17713. |
Still in alpha state. Handles defaults and merging changes with new versions. Enable by setting the HOMEBREW_GIT_ETC environment variable. Closes Homebrew#15751. Closes Homebrew#17713.
See #15737 for background.
I don't think our current approach is sensible. I'd bet that most of our users are not changing etc files and therefore we never upgrade them for these users. This sucks.
You can see an approach I've taken in 8de552e to workaround a specific issue with
redis
.Various solutions I'd suggest (of varying complexity):
etc
files by default and move the old file toetc/blah.conf.old
brew pull
(or whatever people are using) so we detect these issuesetc
file in the tab and we replace it if it didn't changeetc
file (not sure if this is possible or would work) and we replace it if it didn't changeetc
files in a git repository so users can merge changesRegardless I think we need to do something. Thoughts?
The text was updated successfully, but these errors were encountered: