git will break them. It calls unlink and create on every update.
At the moment I am thinking about the GIT_DIR in $HOME/somthing/deeper
and setting the GIT_WORK_TREE to $HOME after cloning, making backups of
possibly already existing files and moving the cloned files to $HOME.
Handling templated configfiles (you don't want your ssh hosts in the
repo) seems to be a bit problematic though.
Any other objections to this method?
--Markus
Am 08.06.2013 01:36, schrieb Dmitrij Czarkoff:
On Fri, Jun 7, 2013 at 10:28 PM, Markus Teich
<markus.te...@stusta.mhn.de> wrote:
* When symlinking files i get problems when moving/backing up the
configfiles in $HOME since it will move the symlink and maybe write an
actual file to $HOME instead.
Hardlinks?
--
Dmitrij D. Czarkoff
