Re: merging back libfoo-java and libfoo-jni

2004-11-23 Thread Adeodato Simó
* Grzegorz B. Prokopski [Tue, 09 Nov 2004 14:21:17 -0500]: > I think mixing native and java code, especially in packages that are in > main and are autobuilt on all architectures is bad idea. I'd kill > libdcop3-java and libdcop3-jni and merge them in either qt or kde > packages (wherever they be

Re: merging back libfoo-java and libfoo-jni

2004-11-09 Thread Grzegorz B. Prokopski
On Fri, 2004-11-05 at 23:05, Adeodato Simó wrote: > [Please CC me on replies, M-F-T set.] > > hi, > > I'm seeking some advice from the Java maintainers as to what would the > best to do in the situation I'll expose. > > currently, kdebindings creates 6 Java library packages: > lib{dcop,q

Re: merging back libfoo-java and libfoo-jni

2004-11-09 Thread Arnaud Vandyck
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sat, 6 Nov 2004 05:05:04 +0100, Adeodato Simó <[EMAIL PROTECTED]> wrote: > [Please CC me on replies, M-F-T set.] > > hi, Yo! > I'm seeking some advice from the Java maintainers as to what would the > best to do in the situation I'll expose. >

merging back libfoo-java and libfoo-jni

2004-11-05 Thread Adeodato Simó
[Please CC me on replies, M-F-T set.] hi, I'm seeking some advice from the Java maintainers as to what would the best to do in the situation I'll expose. currently, kdebindings creates 6 Java library packages: lib{dcop,qt,kde}3-{jni,java}. the Java policy (section 2.4, last paragraph)