Niels Thykier wrote: > I will just give a quick summery, in case you lost the overview of this > debate. > > Currently there are three patches active: > * p1_trival_changes.patch Applied and committed to the SVN. > * p2_fosdem06_r3.patch No change here (yet). The JUnit phrase needs to be modified and I am waiting for feedback on my suggestion. I will apply it with the modified JUnit paragraph, once the exact wording has been worked out. > * p3_fosdem06-gcj.patch Fixed the typo discovered by Eric Lavarde (a "should packages" too much). I have not seen any objections to it, so I will apply it Sunday. Since my $0/year hosting site appears to be down, I have attached the patches again. ~Niels  Actually only the "user"-websites appears to be down; but I hardly think my University would approve if I handed out SSH access to my user account on their machines, so for all intends and purposes /it is down/.
Description: Applies the GCJ part of the FOSDOM 2006 draft. The original proposals have been adapted to better fit the current time. . URL: http://wiki.debian.org/Java/Draft --- policy.xml.orig 2010-03-24 08:49:38.103512020 +0100 +++ policy.xml 2010-03-26 22:18:37.555512280 +0100 @@ -14,6 +14,8 @@ <!ENTITY d-jdk "<emphasis>default-jdk</emphasis>"> <!ENTITY d-jbdep "<emphasis>default-jdk-builddep</emphasis>"> <!ENTITY d-jdoc "<emphasis>default-jdk-doc</emphasis>"> +<!ENTITY JVM "<acronym>JVM</acronym>"> +<!ENTITY JIT "<acronym>JIT</acronym>"> ]> <book> @@ -128,6 +130,11 @@ </para> <para> + The Java bytecode &may; additionally be shipped as machine code, as produced for example + by the GNU Compiler for Java, in a separate architecture-specific package. + </para> + + <para> Programs and libraries &should; enable JUnit tests, if these are present. However, these tests &mustnot; lead to build failures. </para> @@ -311,6 +318,64 @@ </para> </sect1> + <sect1 id="policy-gcj-native"> + <title>Native Java Bytecode (gcj packages)</title> + + <para> + Java bytecode compiled into native code is referred to as + gcj-code and packages containing gcj-code as gcj-packages. + </para> + + <para> + gcj-packages has been added in order to improve + performance of Java libraries and programs. This is + particularly useful on architectures where the JVM + does not have a &JIT;. However, this performance comes + at the cost of size, extra compilation time and + creates architecture dependent packages. + </para> + + <para> + Packages &mustnot; ship gcj-code without the permission of + the Java team (<email>firstname.lastname@example.org</email>). + Source packages that shipped gcj-packages as of March 22nd, + 2010, have been given this permission through the + ratification of this policy. + </para> + + <para> + A request for permission to add gcj should convince + the Java Team that the performance boost of adding + the gcj-packages out-weights the disadvantages. + </para> + + <para> + Source packages compiling gcj-packages &must; Build-Depend on + &d-jbdep;. The gcj-code &should; only be shipped for a selected + set of architectures. + </para> + + <para> + The gcj-code &must; be installed in <filename>/usr/lib/gcj/</filename> + and shipped in a separately from the original jar file. The gcj-package + &must; also install the classmap file generated by aot-compile in + <filename>/usr/share/gcj/classmap.d/</filename>. + </para> + + <para> + The gcj-package &must; call rebuild-gcj-db in the postinst and + postrm script, if rebuild-gcj-db is present. + </para> + + <para> + The gcj-package &must; depend on the package providing the jar + file, it is a native compilation. + The package containing the jar file &must; declare either a + Suggests or a Recommends relationship on the gcj-package. + </para> + + </sect1> + <sect1 id="policy-politics"> <title>Main, contrib or non-free</title> <para>
Description: Applies the FOSDOM 2006 draft. The original proposals have been adapted to better fit the current time. The GCJ changes have been moved to a separate patch. . This excludes the "Java virtual machines" part based on feedback on #365408 URL: http://wiki.debian.org/Java/Draft Closes: #227587 --- policy.xml.orig 2010-03-22 20:04:35.248312944 +0100 +++ policy.xml 2010-03-24 08:44:42.695513119 +0100 @@ -11,6 +11,9 @@ <!ENTITY j2r "<emphasis>java2-runtime</emphasis>"> <!ENTITY jc "<emphasis>java-compiler</emphasis>"> <!ENTITY j2c "<emphasis>java2-compiler</emphasis>"> +<!ENTITY d-jdk "<emphasis>default-jdk</emphasis>"> +<!ENTITY d-jbdep "<emphasis>default-jdk-builddep</emphasis>"> +<!ENTITY d-jdoc "<emphasis>default-jdk-doc</emphasis>"> ]> <book> @@ -119,15 +122,14 @@ <para> Both &must; be shipped as Java bytecode (<filename>*.class</filename> files, packaged in a <filename>*.jar</filename> archive) and with - an "Architecture: all". - It &may; additionally be shipped as machine code, as produced for example - by the GNU Compiler for Java, in a separate architecture-specific - package. + an "Architecture: all". There are rare exceptions to this such as Eclipse + SWT. Exceptions to this rule can only be granted by the Java Team. + Requests &must; be sent to <email>email@example.com</email>. </para> <para> - This policy does not yet address the issue of documentation (for instance - HTML pages made with javadoc). + Programs and libraries &should; enable JUnit tests, if these are present. + However, these tests &mustnot; lead to build failures. </para> <sect1 id="policy-vm"> @@ -257,9 +259,7 @@ </para> <para> - Java libraries &must; depend on the needed runtime environment - (&j1r; and/or &j2r;) but &should; not depend (only suggest) - java-virtual-machine. + Class files in a java library &must; be built with debug symbols. </para> <para> @@ -295,6 +295,20 @@ architecture-specific and follow the usual libXXX[version]-java naming convention. </para> + + <para> + Java library packages &should; compile the javadoc API of the + library. The API &must; link against the javadoc API of the + libraries it depends on. This includes the core java classes, + which are provided by &d-jdoc;. The API &must; be registered with + doc-base and &must; be installed in + <filename>/usr/share/doc/<package>/api/</filename> or + <filename>/usr/share/doc/<package>/api-<component>/</filename>. + </para> + <para> + The API &must; be place in a separate doc package. This package + &must; depend on the doc packages it was linked against. + </para> </sect1> <sect1 id="policy-politics"> @@ -322,6 +336,8 @@ url="http://www.gnu.org/software/classpath">GNU-Classpath</ulink> has a list of free versions), it cannot go to main. If your package itself is free, it &must; go to contrib. + Since java libraries do not have a runtime dependency, + this rule does not apply to them. </para> </listitem> @@ -444,6 +460,11 @@ will be integrated in the policy, one day). </para> </listitem> + <listitem> + <para> + Java packages &should; be built with &d-jdk; if possible. + </para> + </listitem> </itemizedlist> </chapter>
Description: OpenPGP digital signature