On Mon, 2005-02-07 at 11:45 -0500, Jeff Johnson wrote: > Anthony Green wrote: > > >On Mon, 2005-02-07 at 05:58 -0500, Build System wrote: > > > > > >>beecrypt-4.1.2-1 > >>---------------- > >>* Sat Feb 05 2005 Jeff Johnson <jbj@xxxxxxx> 4.1.2-1 > >>- upgrade to 4.1.2 > >>- put java components in sub-package. > >>- check that /usr/lib64 is not used on alpha (#146583). > >> > >> > > > >You called this sub-package beecrypt-java. I suggest renaming this to > >something like beecrypt-java-jni. It only contains the JNI C side of > >the beecrypt java library. The library of java code for beecrypt is > >widely known as "beecrypt-java" (google for beecrypt-java-2.0.0.zip). > >beecrypt-java hasn't been packaged yet, but it will surely require this > >beecrypt-java-jni. > > > > > > Heh, "This space reserved." is perhaps not the right approach. > > Hint: A ptr to what is likely to be the best upstream source for > beecrypt-java-2.0.0.zip > in bugzilla will fix "hasn't been packaged yet" faster than anything. > > Otherwise you'll have to wait until I talk to Bob Deblier in 2 weeks or > so ... > > 73 de Jeff Jeff, Anthony, Please ignore the old beecrypt-java-2.0.0 for now. A new version (mainly a provider offering access to native speed algorithms, requiring the JNI interface) is being worked on, and should start appearing in the BeeCrypt CVS tree shortly. Ideas and thoughts as to which direction that particular package should evolve towards are welcome, as I get little feedback from beecrypt-java users. Although not officially hosted there yet, any bugs or feature requests are always welcome on the BeeCrypt SourceForge page... Cheers, Bob
