WIth the aim to slowly replace all ant/waf uses with Maven/plugins, I've some progress on deb packaging to share and questions to ask:
The WIP patch: http://bhaisaab.org/patches/cloudstack/0001-Maven-jdeb-plugin-for-deb-packaging-WIP.patch (86KB) I'm facing issue on how and which scripts to configure. All the .in, .conf, .properties files are processed by waf and the @variables@ are replaced during that process. These are mostly sysconfig paths and distro dependant env variables, which are actually fixed and standard for debs (Ubuntu/Debian) and rpms (Fedora). All the control files are preprocessed and the artifact Ids and versions are not hard coded in the control files anymore. I need help to verify the control rules, dependencies and to test which file goes where. Every submodule (and every plugin) gets own deb package, same goes for rpm (future). The patch/plugin is inside a profile and can be merge right now, won't break anything. Packaging is very fast compared to waf and does not require any external tool (like dpkg/debuild). For every module or overall project, just cd to the project and do: mvn package -P deb WIP modules: plugins, console-proxy, test, patches/iso, deps/XenServer, awsapi. (they all are somewhat tricky) Right now I've merged all the agent-libs/scripts/deps into one agent-deb. Suggestions and comments? Regards, Rohit
