Linux

60973 readers

1060 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

114

How do you manage your dotfiles? (lemmy.ml)

submitted 2 weeks ago by Flory_Johnny@lemmy.ml to c/linux@lemmy.ml

64 comments fedilink hide all child comments

Hello, i would like to know how you manage your dotfiles.

Do you use some gui or tui?

There are many ways i don't what to do.

Probably im going to do git repo with lazygit. I like tuis. I am managing files on two artix linux systems 1- pc and 2- laptop

you are viewing a single comment's thread
view the rest of the comments

[–] med@sh.itjust.works 7 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

I'm using stow, and then git for versioning. The only question I'm currently facing is whether to keep my stow packages as individual got repos (so I can switch branches for radically different configs or new setups) or treat the whole lot as a big repo, and set the others up as subtrees.

[–] zaubentrucker@sopuli.xyz 7 points 2 weeks ago

IMO you shouldn't use branches for switching between configs. It makes it hard to compose and reuse your configuration.

Just imagine you have a new config file that you now want to add to all of your machines. You'd now have to commit/cherry-pick on all of your branches. Change that file? Now you have to distribute the changes again and might even get conflicts.

Additionally, many programs allow you to change your configuration directory via environment variables (usually XDG_CONFIG_HOME , I think). So you can even keep all machine-specifig configuration files in a single repo under different prefixes for those.