Mailing-List: contact issues-help@aurora.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.apache.org
Date: Sun, 20 Dec 2015 14:37:46 +0000 (UTC)
From: "Stephan Erb (JIRA)" <jira@apache.org>
To: issues@aurora.apache.org
Message-ID: <JIRA.12844227.1436548966000.78086.1450622266606@Atlassian.JIRA>
In-Reply-To: <JIRA.12844227.1436548966000@Atlassian.JIRA>
References: <JIRA.12844227.1436548966000@Atlassian.JIRA>
 <JIRA.12844227.1436548966288@arcas>
Subject: [jira] [Commented] (AURORA-1394) Consistent RPM and Debian packages
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AURORA-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065783#comment-15065783 ] 

Stephan Erb commented on AURORA-1394:
-------------------------------------

Review request: https://reviews.apache.org/r/40877 

> 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)