Re: Java packaging questions about rpmlint messages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jun 29, 2009 at 19:11:55 +0300,
  Ville Skyttä <ville.skytta@xxxxxx> wrote:
> On Monday 29 June 2009, Bruno Wolff III wrote:
> 
> > The included jar files have been removed. I change the property that is
> > used to build the class path to point to the Fedora version of the need jar
> > file (jdom) for building purposes. However after the build the resulting
> > jar file still has a manifest with a classpath in it.
> 
> It should be trivial to get rid of that as well, just search for a MANIFEST.MF 
> template used or the build.xml section that generates it, and patch it out.
> 
> > It seems like the
> > only downside is you can't override the classpath when using the -jar
> > option to run the jar file. That's really the issue.
> 
> It may cause other nasty and hard to debug surprises if another app uses the 
> jar.  Class-Path entries in jar manifests are kind of like RPATHs and should 
> be avoided for the same reasons, at least for jars installed in system jar 
> paths (e.g. /usr/share/java).  
> https://fedoraproject.org/wiki/Packaging/Guidelines#Beware_of_Rpath

OK. It sounds like I need to fix this then (even though I don't expect the
jar to get used by any other packages). I'll deal with it before I submit
the package for review. (I also need to deal with some artwork issues before
I can submit it.)

Thanks for the advice.

--
Fedora-packaging mailing list
Fedora-packaging@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-packaging

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux