Anybody have a solution for dotfiles outside /home


on gentoo for example I have accrued a few files under /etc/portage that to my knowledge just have to live there...

right now I basically rely on my backups for this. but maybe somebody knows a clever way to handle this?

in reply to gkpy

Seems like an odd software choice to create actual dotfiles under /etc. Often files there have much the same name as a user's dotfiles but without the dot. Thinking of things like /etc/profile vs ~/.profile and so on.

Without knowing precisely why those decisions were taken (good reason? ignorance? insanity?) it's not clear what steps to take.

Vaguely leaning towards symlinking or hardlinking but precisely what to do and which way around is still unclear.

Are those dotfiles have your user permissions or are they owned by a system account like root?

in reply to alternateved

Then they shouldn't have dots on them (bad design decision) and should be backed up by the system backup/restore mechanism, whatever that might be, not the user's own homedir backup, which is what I assume OP is talking about.

If they're talking about a full system backup including home directories, that's a moot point because I'd expect they'd be included anyway, dot or not.

in reply to gkpy

I assume by "dotfiles" you simply mean "config files" as there should be nothing in your /etc/portage directory that's hidden. For all configs I want to backup, I just keep a copy of them elsewhere. As for portage stuff, I just copy my make.conf, and everything in each repos.conf and package.* directories.

If you want to simplify a complex solution to an already simple thing, take a look at bare git worktrees.

Linux reshared this.

in reply to gkpy

There should be no dotfiles outside of home directories so I assume you mean a config file. In those cases, git and symlinks are a great option. Make a config directory in your home dir and organize it however you want. Include config files for the tools you’re interested in, commit them to git for backups and then symlink/hardlink the file to the expected path for the application.

madcow doesn't like this.