The Project(Edit)

To solve ~/.* and ~/bin/ in a once-and-for all way.

That is, the system should be:

• Easily distributed. Logging into an account should tell you if it has items that should be push/pulled, and one command should do the sync.
• Easily altered. One short command to edit a file in a way that both $HOME and the working tree are aware of the changes.
• Easily combined. Some people want pieces that other people won't.
• Easily localized. Each machine will have system-specific tweaks, maybe because packages aren't available, for example.

The inputs(Edit)

Many people are working on this idea. I don't know if I'll simply convert to one of their systems, or subsume it and take it further. The "once-and-for all" part means that whatever solution I come up with, it should be good enough that the next guy doesn't have to make this decision - it will be modular enough that he can start from the solution and easily overlay his personalizations.

• vcsh - https://github.com/RichiH/vcsh - From my brief scan, this looks like a good start.
• dewi: 1/7 - https://github.com/ft/dewi - ft's cool system that is sort of like using ExtUtils::MakeMaker in a Makefile.PL
• ft's configs - https://dev.0x50.de/projects/ftdotfiles666 - based on dewi.
• ... - https://github.com/ingydotnet/....git - ingy's ideas are usually pretty good. I haven't looked closely at this one, yet.
• briefcase - http://jim.github.com/briefcase - Another one I haven't really looked at.
• "scp1" - https://github.com/trapd00r/configs - More.
• rking - https://github.com/ryanjosephking/config - My old attempt. Is not much more than a git repo with symlinking.

Going further, a web-based system will be useful. For individual program

configs, something like this might be good:

• Builder UI, like this: http://www.muttrcbuilder.org/page

...more to come.