Literal use of /trinity/local

[mulderij]

In several files the literal string /trinity/local is used. This conflicts with an installation where {{ trix_root }} or {{ trix_local }} are not set to the defaults /trinity or /trinity/local

roles/trinity/luna2/tasks/main.yml
roles/trinity/luna2/templates/luna2-cli-wrapper.j2
roles/trinity/luna2/templates/luna2-daemon-service.j2
roles/trinity/ood-portal/tasks/main.yml
roles/trinity/ood-portal/templates/branding/TrinityX/nginx_stage.yml.j2
roles/trinity/pacemaker/files/pcs
roles/trinity/pacemaker/tasks/main.yaml
roles/trinity/transmission/defaults/main.yml

Possibly related to #395

[aphmschonewille]

thanks! we must have missed it.

[aphmschonewille]

14.4 latest should have mitigated all hard coded references where possible.

There are limitations however that links to a hardcoded path for /trinity/local, for at least our python rpm. I wish there was a way to allow for dynamic paths in a reliable way in rpms and debs. Since we really want to have our own python release bundled w/ trinityx (as some projects don't have pypi builds for 3.11+) and rpms/debs don't have dynamic paths, the configurable paths for /trinity(/local) becomes more or less a hard set. This will hound us for as long as we cannot 100% on the distribution provided pythons.

-A