You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, our environment repos have a layout of something like:
tools/{tool_name}/{os}_{cpu}_archive/
tools/{tool_name}/{os}_{cpu}_executable -> symlink to a file in archive
We could consider updating the layout to something like:
archives/{archive_alias}/
archives/BUILD.bazel # export all dirs
tools/{tool_name}/{os}_{cpu}_executable -> symlink to a file in archive
Which would better support this particular use-case.
It's not obvious whether {archive_alias} should be the filename, filename+sha256, or a user-supplied value in the lockfile. We could add a new 'reference-archive' binary kind that depends on the alias, or we could tie together archives automatically. The specifics here need a bit more of a plan, but something of this shape is probably a thing we'd be willing to adopt in the repo.
The text was updated successfully, but these errors were encountered:
Sometimes, several applicable tools come packaged in the same archive.
@andyscott mentioned in #22 (comment):
Currently, our environment repos have a layout of something like:
We could consider updating the layout to something like:
Which would better support this particular use-case.
It's not obvious whether
{archive_alias}
should be the filename, filename+sha256, or a user-supplied value in the lockfile. We could add a new 'reference-archive' binary kind that depends on the alias, or we could tie together archives automatically. The specifics here need a bit more of a plan, but something of this shape is probably a thing we'd be willing to adopt in the repo.The text was updated successfully, but these errors were encountered: