FR: .tuckrignore

[orca131]

Tuckr symlinks everything by default, which works great for normal configs. The problem is that systemd expects real files in that directory and creates its own symlinks. I think it should be ignored, not cleaned by post-scripts. Please, add the .tuckrignore.

[RaphGL]

Sorry for taking so long for responding, I saw ur issue but didn't have the time to respond.
I should have more time this next month to get back into working more actively on projects.

Can you tell me why you need this? What does systemd do, how does the file structure look like? and is there any docs mentioning it? what are you trying to do?
I really need to know your use case to know how it should behave or whether the solution is actually adding a config file to your config files (which is something I've been avoiding adding and will only add if there really is no better way of achieving what you want)

[orca131]

The problem

I keep my own user units (like swaybg.service) in ~/.config/systemd/user/. When I add this directory, it also pulls in systemd-managed folders such as default.target.wants/, which contain auto-generated symlinks created by systemctl --user enable. These directories should stay under systemd's control. When managing the ~/.config/systemd/user/ directory in my dotfiles package, I need a way to symlink only my custom unit files while skipping certain subdirectories.2

User units live in ~/.config/systemd/user/. Enabling a unit with systemctl --user enable creates symlinks in *.target.wants/ directories inside that location. These are dynamic and managed by systemd, not something you want to version or symlink from dotfiles.1

~/.config/systemd/user/
├── swaybg.service
├── swayidle.service
└── niri.service.wants
     ├── swaybg.service -> ~/.config/systemd/user/swaybg.service
     ├── swayidle.service -> ~/.config/systemd/user/swayidle.service
     └── waybar.service -> /usr/lib/systemd/user/waybar.service

[RaphGL]

While not automatic you could do tuckr add <group> --only-files
This would only symlink the specific service files and let systemd take control of the directory.

If I were to add a tuckrignore for this I'm not sure how I would handle this for every single case that comes up.
Since symlinks are only handled when they're being added I would have to somehow be constantly checking for changes to fix up your directory.

I guess at most I would provide a per group configuration file that lets u set this group to only symlink files or something?
But having a whole config file for a single option feels weird.