On Sun, Feb 08, 2004 at 02:04:04AM -0500, Grzegorz B. Prokopski wrote: > > The difference here is that putting this testing suite in sablevm > package is pretty much impossible to do sanely. Cite from my other mail: > > - if I wanted the test suite to be in SableVM package then it has to be > compiled during the build (and for each build separately) as I cannot > include binary .classes,
This might be a stupid question, but why not? Then you can invoke them in debian/rules for informational purposes - output would be put in the buildd logs. There would be no need for even a binary package as these tests would never be part of any binary package. > - compilation requires not only javac (on which SableVM currently > doesn't build-depend, but let's say it wouldn't be that big problem), > but also jasmin-sable (it's jasmin java assembler maintained by sable > group, as the original author is not interested in it anymore) > - jasmin is packaged as a .deb and is written in java, so it Depends: on > a JVM. > > So it would mean that to compile SableVM JVM package - I would > already need to have a running JVM, which is kinda sick. Or I would need Circular Build-deps suck especialy if the circle becomes an arc :) > to include jasmin source into SableVM source and compile jasmin (which > compilation btw. also requires working JVM), which I percieve as an > insane idea. Isn't SableVM a JVM? :P > The thing is that I am simply unable to manually test before each upload > whether SableVM works well on all architectures. I spent last 5 months > (= ~3 fulltime months) on porting SableVM to these architectures, > ensuring that it works properly and it's still not 100% finished. > > Therefore *I HAVE TO TEST IT* on each architecture, to know whether > there are problems, what they are and to work on removing them. I hope If only Kaffe people did that... - Adam