Packaging guidelines - do we need to repack jars for noarch Java packages?

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

 



G'day!

I've been creating a package for eclipse-nls
<https://bugzilla.redhat.com/show_bug.cgi?id=456972>, and I added this
to my spec file:

# Disable repacking of jars, since it takes forever for all the little
jars,
# and we don't need multilib anyway:
%define __jar_repack %{nil}

I haven't found a good explanation of the reasons behind jar repacking,
but I gather it's something to do with multilib.  What happens if you
don't repack when you should?

Jar repacking is incredibly slow when you have lots of little plugins
(hello Eclipse!), so avoiding it is nice.

I'm pretty sure it's safe to skip repacking in my case, because my
package contains nothing except .properties files inside Eclipse plugins
which are in jars when I download them, but is it safe to do in more
general cases, such as noarch packages?

Is there anything useful we could add to the guidelines?

Regards

Sean.
-- 
Sean Flanigan

Senior Software Engineer
Engineering - Internationalisation
Red Hat

Attachment: signature.asc
Description: OpenPGP digital signature

--
fedora-devel-java-list mailing list
fedora-devel-java-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-java-list

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

  Powered by Linux