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

["Youri Bonnaffé (JIRA)" <ji...@apache.org>]

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

Youri Bonnaffé edited comment on CLOUDSTACK-1415 at 3/9/13 11:30 AM:
---------------------------------------------------------------------

Hello,

>From a master checkout (revision ebafcf826b2506e779c8de8887d867ca4e0306bf), if I run mvn clean install then dpkg-buildpackage -uc -us, I produce all the debian packages.
In the cloud-management script in /etc/init.d I can see CATALINA_HOME=/usr/share/cloud/management whereas the package contains /usr/share/cloudstak-management
Is this expected ? (because the script will not run properly)
Is there work in progress on that ?
I'm can try to contribute a patch if required.
                
      was (Author: youribonnaffe):
    Hello,

>From a master checkout (revision ebafcf826b2506e779c8de8887d867ca4e0306bf), if I run mvn clean install then {code}dpkg-buildpackage -uc -us{code}
                  
> .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