I second this proposal (reproduced below). > I propose to change the following paragraphs in section 2.3 of the > Debian Java policy > > > Programs must have executable(s) in /usr/bin and be executable. They > > can be Java classes (using binfmt_misc) or wrappers. In any case, > > they > > must run without specific environment variables (see Policy 10.9), > > for > > instance CLASSPATH. They must respect the Policy rules for > > executables > > (for instance a manual page per executable, see Policy 13.1). > > > If they have their own auxiliary classes, they must be in a jar file > > in /usr/share/java. The name of the jar should folow the same naming > > conventions as for libraries. > > to: > > Applications must provide one or more executable wrapper script(s) in > /usr/bin. They must run without specific environment variables (see > Policy 10.9), for instance JAVA_HOME or CLASSPATH. They must respect the > Policy rules for executables (for instance a manual page per executable, > see Policy 13.1). > > Additional classes in the package must be packaged in one or more JARs > which can be put into /usr/share/java (if they are intended to be used > by other programs) or into a private directory in /usr/share/<package>. Ben.
Attachment:
signature.asc
Description: Digital signature