-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I am working on packaging logstash
but the build procedure described here
https://github.com/logstash/logstash/wiki/ Building-and-running-logstash-from-source
seems to be incompatible with Fedora packaging. How do other jruby packages (are there any?) deal with this?
http://www.five-ten-sg.com/mapper/logstash/ points to a method to build a "source" rpm, but it is source only if you consider a java .jar file to be source code. At least that lets me install this on multiple machines easily.
Il 30/03/2013 01:16, Carl Byington ha scritto:
I am working on packaging logstash
but the build procedure described here
https://github.com/logstash/logstash/wiki/ Building-and-running-logstash-from-source
seems to be incompatible with Fedora packaging. How do other jruby packages (are there any?) deal with this?
hi, take a look here https://bugzilla.redhat.com/show_bug.cgi?id=821146 regards
http://www.five-ten-sg.com/mapper/logstash/ points to a method to build a "source" rpm, but it is source only if you consider a java .jar file to be source code. At least that lets me install this on multiple machines easily.
Dne 30.3.2013 03:31, gil napsal(a):
Il 30/03/2013 01:16, Carl Byington ha scritto:
I am working on packaging logstash
but the build procedure described here
https://github.com/logstash/logstash/wiki/ Building-and-running-logstash-from-source
seems to be incompatible with Fedora packaging. How do other jruby packages (are there any?) deal with this?
hi, take a look here https://bugzilla.redhat.com/show_bug.cgi?id=821146 regards
http://www.five-ten-sg.com/mapper/logstash/ points to a method to build a "source" rpm, but it is source only if you consider a java .jar file to be source code. At least that lets me install this on multiple machines easily.
Hi guys,
We should reiterate this. There was significant changes in JRuby packaging for F19/Rawhide. We should be able to package it as a gem for JRuby. However, this was never done before, so it will be more or less proof of concept.
We should also clarify naming conventions, macros, etc. Would you mind to join Ruby-SIG ML to discuss this topic there?
Vít