Hallo Daniel, First of all, thanks for this mail!
* Daniel Bonniot wrote: >My proposal is to create a package to hold the tools and the proposed >new policy. I don't think they should be at java-common at this point. >However, if there was a 'new-java-common' (or whatever other name), it There is a 'new-java-policy' package at deb[-src] http://www.katzien.de/debian/java ./ The only thing which is "missing" is, that it includes my example java-config files and will so conflict with packages, which will install such files with the same name. Apart from that: It would be nice, if java-common could include the scripts, even at this point. This scripts doesn't affect the old policy at all and it would make it much easier with installing. So you need to add a apt repository and you don't have the BTS to file bugs against the package (you have my email, though :). Uplaoding it toexperimental/unstable would mean, that it needs to be removed after a change I asked Stefan about including only the scripts in java-common, but he seems to be busy. >would be much easier for all of us to install it, start playing with it, >and see how our packages would work with the new tools. Another They will :) I just uploaded the first 'java-config file included' package: eclipse. I will also try to get a aptch to the j2se-package script, so that the JVMs will include the required files. >advantage would be that whenever there is a change to the proposed >policy/tools, a new version can be uploaded, and all those who have it >installed will get new new version. We can also file bug reports against it. >Jan, are you ready to make this package? I don't think anybody will >object to this, since this does not break anything, and it would be a >step forward. No need to wait for sarge! I will uplaod a new 'proposed-java-policy-tools' package this weekend (I'm dead tired right now :( ) to the above apt site. It will inlcude all the tools and the policy draft. Should I ask for a sponsor to upload it to experimental or unstable? I'm currently speaking with the JPackage guys about having one policy and scripts for JPackage and debian. So far, they seem to opt for a 'add as much API to 'smaller' JVMs, as possible' sollution, effectivly dropping all 'non sun-derived' JVMs, as API isn't ability. Jan -- Jan Schulz [EMAIL PROTECTED] "Wer nicht fragt, bleibt dumm." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
