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

Improve Package Manager architecture #451

praj-foss opened this issue Aug 12, 2019 · 1 comment


Copy link

commented Aug 12, 2019


The new Package Manager API was introduced in #448, which marks our first attempt at a better package handling approach. This API aims to gradually replace the old version classes (like TerasologyGameVersions) and provide better performance and extensibility. Currently, its architecture supports only our Jenkins as the package repository, and also a fixed number of package builds. Its design needs to be upgraded to make it extensible.


  • Support for multiple package repositories
  • Support for package names and versions, instead of an enum of package builds

@praj-foss praj-foss added the GSoC 2019 label Aug 12, 2019

@praj-foss praj-foss self-assigned this Aug 12, 2019

@praj-foss praj-foss added this to Backlog in GSOC 2019: Launcher via automation Aug 12, 2019

@praj-foss praj-foss moved this from Backlog to In progress in GSOC 2019: Launcher Aug 12, 2019


This comment has been minimized.

Copy link

commented Aug 13, 2019

Proposed architecture (taken from Slack):

@praj-foss praj-foss referenced a pull request that will close this issue Aug 17, 2019
3 of 5 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.