Skip to content
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

Support alt dirs with deeply nested tracked files #495

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

ian-h-chamberlain
Copy link

What does this PR do?

Now, as long as there is a tracked file somewhere under the alt directory, it will be linked correctly, instead of requiring the tracked files to be direct children of the alt dir (previous behavior).

What issues does this PR fix or reference?

Closes #490
Related: #328, #356

Previous Behavior

A tracked file had to be a direct child of the ## alt directory for linking the directory to work properly.

New Behavior

Any descendant of the ## alt directory will cause it to be treated as an alt, and the directory itself will be linked (same as previous behavior).

Have tests been written for this change?

Yes: Updated test_alt to use a subdirectory for its contained file as part of the tests. Verified the test failed before my changes and passes after.

Have these commits been signed with GnuPG?

Yes


Please review yadm's Contributing Guide for best practices.

Now, as long as there is a tracked file *somewhere* under the alt
directory, it will be linked correctly, instead of requiring the tracked
files to be direct children of the alt dir.
@@ -461,7 +461,7 @@ EOF
-v distro="$local_distro" \
-v distro_family="$local_distro_family" \
-v source="$input" \
-v source_dir="$(dirname "$input")" \
-v source_dir="$(builtin_dirname "$input")" \
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was just a drive-by cleanup I noticed, from reading builtin_dirname's comment it seems like it should be more portable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant