fix: echo environment variable containing special char

[LordKa0S]

Summary

The PT_install_flags variable is known to contain special characters, which may not be deterministically resolved by the shell unless escaped. It is recommended to quote such variables when using in conjunction with echo.

The unquoted variable is essentially one long character class, [...], and it will match any single-letter filename in the current directory whose name occurs in within the brackets.

source

Additional Context

• https://unix.stackexchange.com/a/347954/663749
• https://unix.stackexchange.com/questions/785504/why-does-the-environment-variable-change-based-on-pwd#comment1505199_785504

Related Issues (if any)

• https://portal.perforce.com/s/detail/500PA00000FWMszYAH

Checklist

• 🟢 Spec tests.
• 🟢 Acceptance tests.

Changes include test coverage?

• Yes
• Not needed

Have you updated the documentation?

• Yes, I've updated the appropriate docs
• Not needed

[CLAassistant]

All committers have signed the CLA.

[ragingra]

@LordKa0S Thanks for making this change. Looks like something that was overlooked. Could you sign the CLA please and I'll get this merged.

[LordKa0S]

@ragingra I've been told that set -o noglob and set -f at the start of the script would have the same effect as (and instead of) quoting. I'll defer to you the choice of implementation that makes the most sense from a project overall perspective.

[LordKa0S]

@ragingra when's the next release?

[ragingra]

@LordKa0S Hoping to get patch release out tomorrow