Do find the patch attached. I have also got the jmx java classes to be compiled (as a part of build process) in this patch. Let me know if the patch looks okay.<br><br>Regards<br>Amit<br><br><div class="gmail_quote">On Tue, Sep 8, 2009 at 8:29 PM, Sebastian Harl <span dir="ltr"><<a href="mailto:sh@tokkee.org">sh@tokkee.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
<div class="im"><br>
On Tue, Sep 08, 2009 at 08:06:38PM +0530, Amit Gupta wrote:<br>
> On Tue, Sep 8, 2009 at 7:05 PM, Sebastian Harl <<a href="mailto:sh@tokkee.org">sh@tokkee.org</a>> wrote:<br>
</div><div class="im">> > On Tue, Sep 08, 2009 at 06:34:04PM +0530, Amit Gupta wrote:<br>
</div><div class="im">> I will start working on the patch.<br>
<br>
</div>Thanks! :-)<br>
<div class="im"><br>
> > > Additionally, the jar files IMO should get published to the lib directory<br>
> > > where the so files are sitting rather than the share directory.<br>
> ><br>
> > Why do you think so?<br>
> ><br>
> > If those files are architecture independent (which, I suppose, is the<br>
> > case, but I'm not sure how JNI has an effect on that), /usr/share/<br>
> > collectd/ is the right place for them (according to FHS).<br>
><br>
> I think of jar files equivalent of .so files. A jar file is used to ship<br>
> collection of java class files similar to a .so file which is a collection<br>
> of object files.<br>
<br>
</div>Yes - this is somewhat similar. Still, .so files are in /usr/lib/ just<br>
because they are architecture dependent.<br>
<div class="im"><br>
> If you look at any of the java based softwares, for<br>
> instance tomcat, you will find all the jars sitting in the lib directory.<br>
<br>
</div>If they are architecture independent, this is not the right place [1].<br>
Have a look at Perl modules. .pm files are similar (in spirit) to .so<br>
files as well - they ship reusable Perl code. While the (architecture<br>
independent) .pm files (Perl code) are usually shipped in /usr/share/,<br>
some modules ship architecture dependent code as well (.so and .bs<br>
files) which are usually sitting in /usr/lib/.<br>
<br>
I'd really like to conform to the FHS as much as reasonably possible and<br>
I don't really see any _real_ reasons not to install (arch. indep.)<br>
.class files in /usr/share/ ;-)<br>
<br>
Cheers,<br>
Sebastian<br>
<br>
[1] Btw., on Debian, the jars are sitting in /usr/share/, see<br>
<<a href="http://packages.debian.org/sid/all/libtomcat6-java/filelist" target="_blank">http://packages.debian.org/sid/all/libtomcat6-java/filelist</a>><br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="h5">Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ <a href="http://tokkee.org/" target="_blank">http://tokkee.org/</a><br>
<br>
Those who would give up Essential Liberty to purchase a little Temporary<br>
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin<br>
<br>
</div></div><br>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (GNU/Linux)<br>
<br>
iEYEARECAAYFAkqmcUIACgkQEFEKc4UBx/zNFACcDzzTRcV+7nFJjcC3h1En7MjQ<br>
JqsAnj6KHo8/T2qW5++PrDR9yvkplrCa<br>
=xFuX<br>
-----END PGP SIGNATURE-----<br>
<br></blockquote></div><br>