Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future direction of repoclosure #190

Open
ehelms opened this issue Apr 16, 2019 · 0 comments
Open

Future direction of repoclosure #190

ehelms opened this issue Apr 16, 2019 · 0 comments

Comments

@ehelms
Copy link
Member

ehelms commented Apr 16, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant