[
https://issues.apache.org/jira/browse/KAFKA-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947880#comment-13947880
]
Joe Stein commented on KAFKA-1324:
----------------------------------
Hi David, I got a failure when running releaseDeb the gradle task is looking
for fsm. So, I jumped to look at your fsm link and there are a few
dependencies in there too that have to be fleshed out. What were your thoughts
on how to include those dependencies in the patch? Maybe a gradle task to
check your Ruby version and gem install fsm when doing the deb release (or
something of the sort)?
Let me know, will finish through trying this later on a vm using fsm and let
you know if any other issues. Looking at the patch got me excited to try it
out, could be really great to have such a nice quick simple support on ubuntu
and an easy path for someone to hook rpm in from your pre-work also.
> Debian packaging
> ----------------
>
> Key: KAFKA-1324
> URL: https://issues.apache.org/jira/browse/KAFKA-1324
> Project: Kafka
> Issue Type: Improvement
> Components: packaging
> Environment: linux
> Reporter: David Stendardi
> Priority: Minor
> Labels: deb, debian, fpm, packaging
> Attachments: packaging.patch
>
>
> The following patch add a task releaseDeb to the gradle build :
> ./gradlew releaseDeb
> This task should create a debian package in core/build/distributions using
> fpm :
> https://github.com/jordansissel/fpm.
> We decided to use fpm so other package types would be easy to provide in
> further iterations (eg : rpm).
> *Some implementations details* :
> - We splitted the releaseTarGz in two tasks : distDir, releaseTarGz.
> - We tried to use gradle builtin variables (project.name etc...)
> - By default the service will not start automatically so the user is free to
> setup the service with custom configuration.
> Notes :
> * FPM is required and should be in the path.
> * FPM does not allow yet to declare /etc/default/kafka as a conffiles (see :
> https://github.com/jordansissel/fpm/issues/668)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
