Closed ibrokemypie closed 2 years ago
Maybe you still have a systemd
folder even after you mv
it?
@ibrokemypie - I looked at your public dotfiles repo. I see the issue. Presently, yadm will only symlink alternate directories if there is at least one tracked file in the root of that directory. I think if you do the following, you should see that link created correctly:
touch ~/.config/yadm/alt/.config/systemd##os.Linux/.empty
yadm add ~/.config/yadm/alt/.config/systemd##os.Linux/.empty
Can you give that a try?
This issue has been labeled as stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue was closed because it has been labeled as stale for 7 days with no activity.
I noticed the same issue.
Just an alt file no directory:
Linking /home/bidar//.local/etc/yadm/alt/etc/systemd/user/emacs.service.d/gdksettings.conf##hostname.odin to /home/bidar//.local/etc/yadm/alt/etc/systemd/user/emacs.service.d/gdksettings.conf
Describe the bug
When trying to move the .config/systemd folder into the yadm alts .config folder (with a condition for os linux) the systemd link/alt is not created after running
yadm alt
. All other alts/links are generatedTo reproduce
Can this be reproduced with the yadm/testbed docker image: Yes
Steps to reproduce the behavior:
mv ~/.config/systemd ~/.config/yadm/alt/.config/systemd\#\#os.Linux
yadm add ~/.config/systemd\#\#os.Linux
yadm alt
Expected behavior
A symlink is created from ~/.config/systemd to ~/.config/yadm/alt/.config/systemd##os.Linux
Environment
Additional context
Output of
yadm list
in ~/.config/yadm/alt/.config (yadm sees the systemd folder and files)Output of
yadm alt
(yadm creates links for all the alts except the systemd one)script.gz