-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
There is a new version available at either
http://www.five-ten-sg.com/util/logstash.fedora.tar.gz or hg clone http://hg.five-ten-sg.com/logstash
I found and patched the problem with logstash finding the elasticsearch jar files. That path should be specified via a command line switch. This version seems to run properly, but the following issues still need work:
1) the elasticsearch build (using maven) downloads prebuilt .jar files and bundles them.
2) the logstash build still downloads prebuilt gems and bundles them.
Is there a document to read regarding proper fedora packaging of jruby gems?
Hi Carl,
I am going to comment only on elasticsearch at this moment, but I believe that this comments applies also for other packages (although I did not checked them).
* Please focus on Fedora There is no JRuby on EPEL/RHEL, so any tag trying to make some adjustments is distracting. This packages will be peculiar even without them. Please remove them.
* Source URL: You can get the tarball using https://github.com/elasticsearch/elasticsearch/archive/v0.20.5/elasticsearch..., so in your case, it should look like: https://github.com/%%7Bname%7D/%%7Bname%7D/archive/v%%7Bversion%7D/%%7Bname%...
* You should always expand the archive in %prep section, using %setup macro
* You should be using %global instead of %define
* You should not install anything into /usr/local
* You should be following Java packaging guidelines for this package, especially the maven section [1]. Since I am not expert on Java, I would suggest to seek java-sig for help with this particular package.
Vít
[1] https://fedoraproject.org/wiki/Packaging:Java#Apache_Maven
Dne 17.4.2013 22:15, Carl Byington napsal(a):
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
There is a new version available at either
http://www.five-ten-sg.com/util/logstash.fedora.tar.gz or hg clone http://hg.five-ten-sg.com/logstash
I found and patched the problem with logstash finding the elasticsearch jar files. That path should be specified via a command line switch. This version seems to run properly, but the following issues still need work:
- the elasticsearch build (using maven) downloads prebuilt .jar files
and bundles them.
- the logstash build still downloads prebuilt gems and bundles them.
Is there a document to read regarding proper fedora packaging of jruby gems?
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux)
iEYEARECAAYFAlFvAtQACgkQL6j7milTFsFqrACcDO2W5TrDv+HVRT5LuzhDkCuS A8EAniPTSjXC5Oa4KM63b6qoY/93hPS8 =I5dr -----END PGP SIGNATURE-----
ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 2013-04-18 at 07:49 +0200, Vit Ondruch wrote:
- Please focus on Fedora
There is no JRuby on EPEL/RHEL, so any tag trying to make some adjustments is distracting. This packages will be peculiar even without them. Please remove them.
The client funding this is using RHEL/Centos on servers. It is a fixed requirement here that these packages build/install on Centos6.
- You should not install anything into /usr/local
Yes, that was a temporary hack before I found the java packaging guidelines. I am working on this today.
ruby-sig@lists.fedoraproject.org
-
Carl Byington -
Vít Ondruch