how to manage a file under a directory that itself is a managed symlink?

[laur89]

~/.gradle is a symlink:

$ cat ~/.local/share/chezmoi/symlink_dot_gradle
/data/repositories/gradle

Is it possible to manage a ~/.gradle/gradle.properties file and make it get deployed to the symlinked target? Handling it via run_* scripts is feasible, but trying to avoid using them as much as possible.

---

Loosely related: #3702

[halostatue]

Not really, especially as /data/repositories/gradle is outside of $HOME.

Your best bet would be to create a gradle.properties that is written to ~/.config/gradle/gradle.properties and have an after script create a symlink from ~/.config/gradle/gradle.properties to ~/.gradle/gradle.properties.

[laur89]

create a gradle.properties that is written to ~/.config/gradle/gradle.properties and have an after script create a symlink from ~/.config/gradle/gradle.properties to ~/.gradle/gradle.properties

Been using symlink-based dotfile managers thus far, and the main reason I'm migrating to cz is to get away from the symlinks. I do prefer them personally, but binding select files & dirs to e.g. sandboxes makes it really difficult.

[halostatue]

create a gradle.properties that is written to ~/.config/gradle/gradle.properties and have an after script create a symlink from ~/.config/gradle/gradle.properties to ~/.gradle/gradle.properties

Been using symlink-based dotfile managers thus far, and the main reason I'm migrating to cz is to get away from the symlinks. I do prefer them personally, but binding select files & dirs to e.g. sandboxes makes it really difficult.

The problem is that you can't really manage inside a symlink directory. If your gradle directory was within $HOME, it's an entirely different matter.