DM-35510: Only set binary root for x86_64 arch. #163
Conversation
| url="$binary_root/env/${eups_tag}.env" | ||
| else |
There was a problem hiding this comment.
I'm confused on why given an env hash this must fail for src installations?
There was a problem hiding this comment.
Because exact envs are only recorded for tarball builds. An exact env has platform-specific conda packages in it, so it's not meaningful to preserve it with source tags.
There was a problem hiding this comment.
Ah I would have figured it would have been the resolved env at the time of tagging a given product, but I understand the limitations as they exist currently.
There was a problem hiding this comment.
Even conda env export has platform-specific packages (e.g. _sysroot_linux-64_curr_repodata_hack=3=h5bd9786_13). I don't think there's any way to get a platform-independent "resolved" env beyond the rubin-env version number.
There was a problem hiding this comment.
Wouldn't it be the union of the exact versions of the packages in the env, and their dependencies? I guess that could keep growing, like you say until you got to platform specific packages. I wonder if the set of those are small enough to be enumerated and not considered in src builds? Maybe its not worth the time.
No description provided.