Details
-
Story
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Aurora comes with the necessary artifacts to create DEB und RPM packages. Unfortunately, the packaging is not really consistent. This is confusing for users, but also a burden for Aurora maintainers.
Some examples:
- different handling of gradle (auto-download vs dependency which has to be build manually)
- different packages names (e.g., aurora-client vs aurora-tools)
- different configuration mechanism and default config options
Attachments
Issue Links
- relates to
-
AURORA-951 Debian packaging for Aurora
- Resolved
-
AURORA-1116 RPM packaging for Aurora
- Resolved
-
AURORA-1393 Publish nightly and release packages for major operating systems
- Resolved