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
I wanted to capture converstion from repoclosure discussions on where we want to eventually land with their design in package_manifest:
I think this is fine for now. I do think we should be aiming to use tags as the connector. I think our current tito usage makes this difficult since releasers mask 1-N tags vs. iterating over a set of tags. What I am essentially saying is we should think about how we can get to a model of:
packages have tags
for each tag a repoclosure config exists
a package is built, and downloaded to a directory by tag name for each tag
repoclosure is applied to those
I assume that model would require quite a bit more work and re-factoring, so this model works for now.
The text was updated successfully, but these errors were encountered:
I wanted to capture converstion from repoclosure discussions on where we want to eventually land with their design in package_manifest:
The text was updated successfully, but these errors were encountered: