Joe Smith <unknown_kev_cat <at> hotmail.com> writes: > I understand that. What I was saying is that it seemed odd that upstream had > not done this. It may be a wise dea to prod upstream and see if they will > update for 3.2. I doubt the breakage is too severe.
They may, but not this early in the release cycle. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=98371 for details. > The new packages run on kaffe? (it sounds that way, If you used a different > free jvm them just 's/kaffe/[name of other JVM]/' for the following > questions.) Afaik, yes. And on gcj/gij. And surely on the various other up-to-date free runtimes in Debian, since they all use pretty much the same class libs :) > Did you remove the depends on an 'offical' JVM, or do 'kaffe|...'? > If you removed the depends on the 'offical' JVM rather than make it a > choice, please reconsider. Explanation: I have a JVM from sun installed on > my system solely for reasons of practicallity. Since I already have that > installed, and that is known to run Eclipse just fine, I do not want to > waste space downloading kaffe. It'd be impossible to move it main, afaik, if it only depended and worked on non-free software. If you want to avoid a $freevm download completely, you'd have to make sure that the eclipse 3.1 package and all its dependencies build and work fine on the non-free software in question, and don't mess with the non-free software's licensing restrictions, for example. That's quite a chunk of work, and since the manpower of the debian-java effort is limited, most people doing the actual packaging work tend to concentrate their efforts on Free Software, which Debian can distribute freely together. cheers, dalibor topic -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
