-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alternate directories need to have a managed file at the top level #328
Comments
I just ran into this problem as well. My current workaround is to put a managed .placeholder file in the directory, but agree it should be handled correctly within yadm. |
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 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. |
Why does the file need to be at the top-level? Is there a reason why yadm has such a requirement? I don't understand why it's not ok to have the files deeper in the directory hierarchy... I'm asking because this issue was fixed by updating the documentation instead of accepting files deeper in the directory hierarchy. |
Alternate directories need to have a managed file at the top level.
The documentation says that "Links are also created for directories named this way, as long as they have at least one yadm managed file within them." It should either be corrected to point out that they need a file at the top level, (ok) or yadm should be fixed work as advertised. (better!)
To reproduce
Add this and it works:
Expected behavior
I expected an alternate symlink.
Environment
Additional context
Debugging, trying to figure this out, I came to this, which (I think) strips one level: "${tracked%/*}", here on line 639:
The text was updated successfully, but these errors were encountered: