bin-env-setup: let the suite compute its own unique ID
There is no way for poulpe itself to determine all the parameters that actually *uniquely* define a bin-env, because it has no knowledge of how to gather its dependencies, for example. We have to assume that bin-envs in general wouldn't survive being moved/renamed, because any hardcoding of the path that would happen in its setup would get broken. Thus, we setup this contract with the suite setup that the unique ID is indeed unique to all relevant parameters for this particular bin-env.
parent
5dc622c6
No related branches found
No related tags found
Please register or sign in to comment