On Thu, Feb 05, 2004 at 08:11:30PM -0500, Grzegorz B. Prokopski wrote: > W li?cie z czw, 05-02-2004, godz. 14:43, Adam Majer pisze: > > we can add a new Arch:all package. It makes sense to me either way, but
> Adding a new resulting Arch:all package-does such move buy us anything? I meant the source; never clear on these things. :) It was either combine the things to avoid the build-dep loop or to create a new source. I think it might have got rejected since you called it sablevm-test-suite which would intuitivly make sense to put in the SableVM. People might think of it like the gcc test suite that is part of the gcc source. > > Also, why not combine sablevm and sablevm-classlib source? > For similar reasons. These are distinct packages. Distinct upstreams > (99.5% of sablevm-classlib is GNU Classpath). Updated at different > intervals (sablevm is updated much more often, and there's no point > rebuilding native part of GNU Classpath on each SableVM upload). > Note: SableVM is not Kaffe, which includes much more things than a JVM. > SableVM Project focuses on the JVM. > > I really appreciate other things that you've pointed out in the other, > private email, but these to which I answered above - I strongly dislike > and oppose. Well, one of the things was to combine the sources which doesn't make sense anymore, and the other was suppose to be source package for the sablevm-test-suite (which I of course called "Arch:all". Don't ask why :) > I hope Daniel will forgive us polluting his mailbox :-) I think most email boxes need competition to the [EMAIL PROTECTED]@ crap. > PS: Can we declare EOT? Or at least not involve Daniel in the possible > furhter disucussion. > > I would like to hear whether *HE* has any questions or I can just > reupload the package. Daniel? I don't have objections to the new source package. I just asked if one could make it part of SableVM as it sounds like it is a part of it (almost like jikes and jacks), but I guess they are not. Sincerely, Adam I think that the biggest problem might be the description of the sablevm-test-suite Description : various java tools used to test SableVM JVM To assure SableVM is operating properly on wide range of platforms it is best if it can be tested easily, quickly, often and throughly. This package contains set of tools, partially specific to SableVM, which should help finding and diagnosing possible problems before they hit the users. Why do we need this in Debian? It seems from the description that sablevm-test-suite is something that is specific to SableVM and is used by the SableVM developers to prevent regression bugs, etc.. Could you explain why should this be in the archive? Who would use this package?
