vcsh – Version Control System for $HOME

Re:vcsh – Version Control System for $HOME by chubot on Saturday January 02, 2016 @01:26AM (#10825329)

What I do is just have a ~/git/dotfiles repo, and then 'ln -s ~/git/dotfiles/vimrc ~/.vimrc' (and there is a script to dot his in the repo). Same with .bashrc, etc. You an use the same repo or different repos.

How is this better?

[ Parent | on HN ]

Re:vcsh – Version Control System for $HOME by ohthehugemanate on Saturday January 02, 2016 @03:06AM (#10825499)

Exactly what I do. It has the added benefit of only requiring the systems I already require (bash and git), so no extra software install or learning.

[ Parent | on HN ]

Re:vcsh – Version Control System for $HOME by unfunco on Saturday January 02, 2016 @10:26AM (#10826413)

I maintain a single dotfiles repository also, and have found RCM by Thoughtbot[0] to be an excellent tool for managing said dotfiles.

[0]: https://github.com/thoughtbot/rcm

[ Parent | on HN ]

Re:vcsh – Version Control System for $HOME by vok5 on Saturday January 02, 2016 @04:03AM (#10825617)

You could also use GNU Stow, which is a symlink farm manager. Here's an example on how to use it with dotfiles: https://github.com/dmarcoux/dotfiles

[ Parent | on HN ]

Re:vcsh – Version Control System for $HOME by daveguy on Saturday January 02, 2016 @01:36AM (#10825338)

This eliminates the ln -s ~git/dotfiles/vimrc ~/.vimrc step. Or more specifically, allows you to have any number of subsets of files contained in a single directory (or subdir) as members of different repositories.

[ Parent | on HN ]

Re:vcsh – Version Control System for $HOME by chubot on Saturday January 02, 2016 @04:03AM (#10825616)

Yeah, but I'd rather just have a 5 line shell script in my repo listing all the files it manages, rather than entirely new tool. I think it's overkill for dotfiles. A shell script works.

[ Parent | on HN ]