[
https://issues.apache.org/jira/browse/AURORA-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622695#comment-14622695
]
Benjamin Staffin commented on AURORA-1394:
------------------------------------------
My goals when putting together the Debian packages was to be consistent with
the way things normally work on Debian and Ubuntu systems, so there may be some
places where distro philosophical differences apply. My familiarity with
RPM-based systems is quite rusty, but I bet most of the differences can be
resolved.
aurora-tools vs aurora-client: I called it aurora-tools to distinguish it as
being tools related to working with Aurora, rather than platform/system
components.
Config mechanism: It's traditional for knobs to be exposed in
/etc/default/<thing> on Debian-based platforms. On Redhat I think that's
/etc/sysconfig/<thing>.
Build process: In theory it's best if package build processes don't involve
downloading things from the internet, but that's pretty hard to achieve with
gradle and pants builds. I figured we could at least get gradle itself from
apt if feasible. Perhaps that deb could come from a hosted apt repo somewhere?
> Consistent RPM and Debian packages
> ----------------------------------
>
> Key: AURORA-1394
> URL: https://issues.apache.org/jira/browse/AURORA-1394
> Project: Aurora
> Issue Type: Story
> Reporter: Stephan Erb
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
