Paul Cager a écrit : > Hi Yann, > > I'm not a DD so I would not be able to help you upload the package, but > there are others on the list who could do that when you are ready. A few > comments to be going on with... > > 1) You build openfire using Sun Java. Does it fail to build with a free > Java implementation? If it could be built with a free Java more people > would probably be interested in helping.
I didn't yet try to build openfire with a free jvm, that's on my todo list but I want first to produce a working and compliant package that uses sun java jvm. But I suspect I will have some problem with free jvm, quoting one openfire developper: "Openfire uses at least one thing that's specifically a "sun proprietary library" ... which may or may not be in this IceaTea build." > 2) If it can't be built with a free Java, then openfire would have to go > into contrib (not part of the core debian distro). You'd need to amend > your debian/control for this. Ok I will do that. > 3) The orig.tar.gz is almost 50Mb, and includes what looks to be a Java > runtime (I'd guess a Sun one). This would should be removed from the > upstream tarball. I am currently maintaining the package in a version control system with MergeWithUpstream enabled. I use bzr-builddeb. Do you know how I can change the upstream tarballs with that configuration ? > 4) There are many other jars in the tarball, and these should be removed > as well (even though you have included their copyrights/licenses in > debian/copyright). Generally binaries are not allowed in the orig.tar.gz > files (because of potential licensing issues, concerns about if the > package [and its dependencies] can be built from free source, size of > archive etc). So this means I have to make a debian package for all the jars that are not in debian. Outch, this will really be a lot of work. Openfire uses 30/40 java libraries that are not packaged in Debian. > You would normally also prune the Javadocs etc and > regenerate them in your debian build. Ok I will do that. > 5) The compiled Jars should normally live in /usr/share/java (symlinked > from elsewhere if necessary). I think you have got them the other way > around. The Jars are also normally versioned as well (e.g. junit.jar -> > junit-3.8.1.1.jar). Even jars only used by openfire should go in /usr/share/java ? > 6) Are you sure the postinst is necessary? The mkdirs / chowns etc could > be done as part of debian/rules. Ok, i will change that. > I hope this helps, Definitely ! Thanks for your help. I will soon produce a new package that will solves some of the issues you raised. Yann -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
