From 4d4966483b12ade6cc63a0fe129351c09470b253 Mon Sep 17 00:00:00 2001 From: Ola Nordmann Date: Wed, 25 Sep 2002 06:05:37 +0000 Subject: Is no longer proposed, some editorial things, libraries should only suggest java-virtual-machine. --- debian/changelog | 4 ++++ policy.xml | 59 +++++++++++++++++++++++++------------------------------- 2 files changed, 30 insertions(+), 33 deletions(-) diff --git a/debian/changelog b/debian/changelog index e47e311..b70d77c 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,6 +1,10 @@ java-common (0.15) unstable; urgency=low * Removed policy.sgml from source. + * Changed so that the policy is no longer PROPOSED. + * Some editorial changes. + * Java libraries should now only suggest java-virtual-machine, + closes: #159448. -- Ola Lundqvist Wed, 25 Sep 2002 07:41:45 +0200 diff --git a/policy.xml b/policy.xml index 76d80c9..d423c66 100644 --- a/policy.xml +++ b/policy.xml @@ -14,7 +14,7 @@ - PROPOSED Debian policy for Java + Debian policy for Java $Revision:$ $Date:$ @@ -67,19 +67,6 @@ Background - - An important warning: this text is - a proposal. I put it here, publically, so it can - be read, discussed, implemented, ignored, etc. It has no sort of - endorsement from any authority in Debian or elsewhere. - - - Feel free to report me (Ola Lundqvist - opal@debian.org) comments and disagrements. I'll - put them on this text and forward them to - debian-java@lists.debian.org, if you don't object. - - There are several "subpolicies" in Debian. They all want to make the @@ -93,21 +80,18 @@ - This policy is intended to be in a package java-common, whose - maintainer will be Java Debian - debian-java@lists.debian.org, when the policy have been - officially accepted. + Feel free to report comments, suggestions and/or disagrements to the + java-common package (java-common@packages.debian.org) + or the Debian Java mailinglist + debian-java@lists.debian.org. Change requests should + be sent as a bug to the java-common package. + Policy - - A package java-common is created, containing this policy and - some basic tools. - - Virtual packages are created: &jc;, &j2c;, &jvm;, &j1r; and &j2r;. @@ -116,8 +100,7 @@ Packages written in Java are separated in two categories: programs and libraries. Programs are intended to be run by end-users. Libraries - are intended to help programs to run and to be used by developers. - Both &must; depend on &jvm;. + are intended to help programs to run and to be used by developers. @@ -190,14 +173,18 @@ Policy 6.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. + + 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. - Programs &must; depend on &jvm; and the needed + + Programs &must; depend on &jvm; and the needed runtime environment (&j1r; and/or &j2r;). - There is no naming rules for programs, they are ordinary programs, + + There is no naming rules for programs, they are ordinary programs, from the user point of view. @@ -207,7 +194,7 @@ Libraries are not separated between developers (-dev) and users - versions, since it is meaningless in Java. + versions, since this is meaningless in Java. @@ -234,12 +221,18 @@ version of the available packagename-extraname-version.jar files. - + + + Java libraries &must; depend on the needed runtime environment + (&j1r; and/or &j2r;) but &should; not depend (only suggest) + java-virtual-machine. + + All jar files &must; have a well-documented CLASSPATH, so that developers should know what to add to their wrappers. - + This applies only to libraries, not to the core classes provied by a the runtime environment. -- cgit v1.2.3