Your scheme is sound in theory, but isn't a solution for Java under the Debian OS. It means that virtually all Java packages in Debian would sit in contrib. That's just not acceptable.
Now that I am putting some real effort into Kaffe again I would like to see an actual functioning framework of Java applications in main. There is no Free VM that I am aware of that supports either Sun's 1.4 or 1.3 or even 1.2. Your solution doesn't fulfill the Social Contract and not even Java is specially immune. I do see your point about alternatives. If we constrain my suggestion to just base VM classes that problem goes away. Base class libraries are not currently shared by any VMs I am aware of. Such an effort would be a worthy cause but it isn't likely to happen anytime soon. Instead of giving me a flat "that won't work" can you see a way to modify my approach? Is there some way that a classpath could be constructed from functional dependencies in a way that works for more than base classes? Or is my criticism of your scheme unfounded? On Wed, 2003-08-27 at 19:45, Jan Schulz wrote: > I see what you mean, but this will simple not work: How do you want to > use alternatives? [ SNIP ] > I prefer a free VM, but much more I prefer a *working* VM. -- _____________________________________________________________________ Ean Schuessler [EMAIL PROTECTED] Brainfood, Inc. http://www.brainfood.com
