"Grzegorz B. Prokopski" <gadek@debian.org> writes: > W liście z pon, 07-06-2004, godz. 04:28, Arnaud Vandyck pisze: >> "Grzegorz B. Prokopski" <gadek@debian.org> writes: >> >> > I could not add libgnujaxp-java as a Dependency of sablevm, because this >> > -java package depends on some native pieces (libgnujaxp-jni) that are >> > not available on one of the platforms SableVM supports in Debian. >> > Probably a wishlist bug against jaxp package would be in order. >> >> I thought jaxp was included in sablevm? > > The sources are included in sablevm-classlib, because that's what the > upstream does, but they are not built nor installed. hehe ;-) I should retry gjdoc with sablevm ;-) >> You should event Provides: jaxp, don't you? > > Hmm... libjaxp1.2-java doesn't provide a virtual package called > "jaxp". No virtual package, you are right. I thought you could just provide libgnujaxp-java, but it's impossible because sablevm (even if gnujaxp *is* in the classlibs) will not install /usr/share/java/gnujaxp.jar. Soory. > But to answer your question: even if we had this code included in > our basic class libraries, it wouldn't replace & conflict & provide > "jaxp". sight. > Inside our class-library sources we should have a better handling > of such situations. I am working on it. But this is not a showstopper > for now, I think. And I wouldn't want to just include this code into > Debian archive once again, w/o any visible benefit, when there already > exist a package that provides this functionality and using it seems to > work just fine. You are right. But I think integrating gnujaxp in sablevm could be a good thing to sablevm in general... Cheers, -- .''`. : :' :rnaud `. `' `-
Attachment:
pgpgR0xyEd1xA.pgp
Description: PGP signature