You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Noa Resare (JIRA)" <ji...@apache.org> on 2013/04/05 17:51:15 UTC

[jira] [Resolved] (CLOUDSTACK-1415) .deb packaging merge

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Noa Resare resolved CLOUDSTACK-1415.
------------------------------------

    Resolution: Fixed
    
> .deb packaging merge
> --------------------
>
>                 Key: CLOUDSTACK-1415
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1415
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Noa Resare
>            Assignee: Noa Resare
>
> This ticket tracks the merge of the packaging work that me and [~widodh] has been working on in a separate branch.
> The diff is kind of large, but most of the lines are the package delimitations moving around resulting in a lot of file moves. The changes should be orthogonal to non-packaging related developments and the target is both the 4.1 and master branches. Since the current state of packaging is very broken, at least it will be an improvement.
> Concepts included in the diff:
> * the replace.properties location used by maven is parameterized to allow for a build that does not modify the currently git tracked files
> * package naming is updated along the lines of what was discussed on the -dev mailing list and between committers at the Build a Cloud Day in Belgium.
> * package version pattern is updated (since we redo all package names, we might as well drop the epoch)
> This commit is not very well tested, and most likely broken in a few ways, but since should be pretty safe regression-wise and it is a good starting point to get to a broader user base for the last fixes to 4.1 packaging.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira