What are best practices for having a repo that feeds into system configuration?
The problem is that Git repos are not stable; ie if you mess it up you would mess up your system if the system files are symlinked to it. So you either have to install the files into their final destination or symlink them from another staging directory which seems a bit pointless. It's attractive to just symlink it into the repo directly but just not very reliable. I guess I should let go of the idea of using symlinks even though it is very convenient. It means actual files are all together if you want. But having files in a intermediate staging directory creates the problem of having to push files back into the repo after you edit them. Or, you always edit in the repo, but this is weird when you have a staging directory that is suitable for it. Therefore I guess the best choice would be to use direct installation from the repo into final destinations directly. Otherwise you would definitely be tempted to edit them outside of the repo. What do you do in such a circumstance? -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
