Manual control over TurboActivate files locationAnswered

Hi, while reading instructions on using TurboActivate with Python I came across a note about TA_USER vs. TA_SYSTEM. What I read there made sense and was clear, but it raised a follow up question(s):

1. Is it possible to configure the specific location where the TurboActivate internal data will be stored?
2. If location configuration is not possible, is the location path predetermined for each of the modes (TA_USER vs. TA_SYSTEM)?

In case it helps with providing a better answer, the reason behind my question is that we release products as RPM artefacts and manage all paths necessary/used by the product via RPM mechanisms: ensuring that paths exists or are created and have correct ownership/permissions. So it would be desirable for us to pre-define all LimeLM related paths (fingerprint location, .dat file location, etc…) rather than deal with unknown/dynamically selected paths.