Difference between revisions of "Talk:Dotfiles"

From ArchWiki
Jump to: navigation, search
(Shell frameworks: rm closed)
(Some other tools, not package but might be of interest.)
Line 7: Line 7:
  
 
:Almost. Although it's hiding rather than excluding, there's one important difference — the actual repo is in a sub directory, not the base of $HOME. This means when you're sitting in the $HOME tree, attempting to run any vanilla git commands will fail (as it's not a repo). This protects you a little, but also stops any git cruft from showing for users running with git aware prompt strings (i.e. showing current branch / state). You could add a wildcard exclusion to this method as well, but it would come with the tradeoff of losing visibility of what you don't have tracked in your dotfiles.--[[User:Kimburgess|Kimburgess]] ([[User talk:Kimburgess|talk]]) 23:52, 26 December 2016 (UTC)
 
:Almost. Although it's hiding rather than excluding, there's one important difference — the actual repo is in a sub directory, not the base of $HOME. This means when you're sitting in the $HOME tree, attempting to run any vanilla git commands will fail (as it's not a repo). This protects you a little, but also stops any git cruft from showing for users running with git aware prompt strings (i.e. showing current branch / state). You could add a wildcard exclusion to this method as well, but it would come with the tradeoff of losing visibility of what you don't have tracked in your dotfiles.--[[User:Kimburgess|Kimburgess]] ([[User talk:Kimburgess|talk]]) 23:52, 26 December 2016 (UTC)
 +
 +
== Some other tools that I found that might be of use ==
 +
 +
Hi,
 +
 +
I didn't realize adding adding these tools had to be packaged in arch, these few aren't yet. I'll put them here in the discussion area in case anyone is interested in checking them out. I am not sure if they offer anything that the other ones don't.
 +
 +
* {{App|dotbot|Dotbot is designed to be lightweight and self-contained, with no external dependencies and no installation required. Dotbot can also be a drop-in replacement for any other tool you were using to manage your dotfiles, and Dotbot is VCS-agnostic -- it doesn't make any attempt to manage your dotfiles.|https://github.com/anishathalye/dotbot}}
 +
* {{App|dotstow|Features: Group dotfiles into units (stow packages), Automatically symlink (stow) files, Backup dotfiles with git |https://github.com/codejamninja/dotstow}}
 +
* {{App|freckles|freckles is written in Python, and uses Ansible to do the heavy (system- and state-management) lifting.|https://github.com/makkus/freckles and the article about it https://freckles.io/blog/managing-dotfiles}}
 +
 +
 +
I'm still researching what I am going to use myself. So many tools!

Revision as of 18:27, 15 July 2018

Bare repository and alias method

Hi all, I'd love to expand this out to include the method coved in this HN discussion. The simplicity of it is rather beautiful and it keeps the tracking isolated from the rest of $HOME. Before I do that, I'm new here so don't want to just start making sizeable edits with some form of discussion. Can anyone see any advantages of the currently listed gitignore method that this does not provide? -- Kimburgess (talk)

So basically all it does is hide the untracked files in the commit window? IOW, a half-baked variant of Dotfiles#Using_gitignore which actually ignores the files instead of hiding them. One example where this is better if you end up running git clean. If the files are not ignored, they'd end up deleted. -- Alad (talk) 12:51, 26 December 2016 (UTC)
Almost. Although it's hiding rather than excluding, there's one important difference — the actual repo is in a sub directory, not the base of $HOME. This means when you're sitting in the $HOME tree, attempting to run any vanilla git commands will fail (as it's not a repo). This protects you a little, but also stops any git cruft from showing for users running with git aware prompt strings (i.e. showing current branch / state). You could add a wildcard exclusion to this method as well, but it would come with the tradeoff of losing visibility of what you don't have tracked in your dotfiles.--Kimburgess (talk) 23:52, 26 December 2016 (UTC)

Some other tools that I found that might be of use

Hi,

I didn't realize adding adding these tools had to be packaged in arch, these few aren't yet. I'll put them here in the discussion area in case anyone is interested in checking them out. I am not sure if they offer anything that the other ones don't.

  • dotbot — Dotbot is designed to be lightweight and self-contained, with no external dependencies and no installation required. Dotbot can also be a drop-in replacement for any other tool you were using to manage your dotfiles, and Dotbot is VCS-agnostic -- it doesn't make any attempt to manage your dotfiles.
https://github.com/anishathalye/dotbot || not packaged? search in AUR
  • dotstow — Features: Group dotfiles into units (stow packages), Automatically symlink (stow) files, Backup dotfiles with git
https://github.com/codejamninja/dotstow || not packaged? search in AUR
  • freckles — freckles is written in Python, and uses Ansible to do the heavy (system- and state-management) lifting.
https://github.com/makkus/freckles and the article about it https://freckles.io/blog/managing-dotfiles || not packaged? search in AUR


I'm still researching what I am going to use myself. So many tools!