Because variables can be overridden, it's a good idea to make sure that the recipe will still work even if a non-default variables used. One issue that would prevent recipes from running is using a NAME variable in paths that should be hard-coded (e.g. /Applications/Foo.app).
This PR removes the NAME variable from all file paths and replaces it with the actual app name, which should make the recipe more resilient for overrides.
Because variables can be overridden, it's a good idea to make sure that the recipe will still work even if a non-default variables used. One issue that would prevent recipes from running is using a
NAMEvariable in paths that should be hard-coded (e.g./Applications/Foo.app).This PR removes the
NAMEvariable from all file paths and replaces it with the actual app name, which should make the recipe more resilient for overrides.