Best practices: .chezmoi.sourceDir vs absolute path?

[HelloGrayson]

What's the case for using .chezmoi.sourceDir in templates and scripts vs ~/.local/share/chezmoi?

In my dotfiles project I've been using the following pattern in bash scripts:

WORKINGDIR="$(chezmoi data | jq .chezmoi.sourceDir -r)/src/backup"

bash "$WORKINGDIR/init-systemd.sh"

This grants scripts reliable access to eachother during a Chezmoi run.

Is there some advantage to this as opposed to the following convention?

WORKINGDIR="$HOME/.local/share/chezmoi/src/backup"

bash "$WORKINGDIR/init-systemd.sh"

For example, under what circumstances can the sourceDir change, or is that a constant?

Thanks for the feedback.

[twpayne]

If you're always going to use ~/.local/share/chezmoi as your source directory you can use the fixed path.

Since some people want to use different directories (e.g. ~/dotfiles or ~/repos/dots or whatever), many examples in chezmoi's documentation use the .chezmoi.sourceDir template variable or chezmoi source-path command for portability. These also account for the user's .chezmoiroot setting.

[HelloGrayson]

That explains it.

So ultimately users can make their chezmoi source path portable if needed. In that case I think I will use the absolute path, simplifying my scripts, until such a need arrives.

Thank you, @twpayne.