[openglean-devel]OpenGLEAN 0.4.1 is out.

[Richard R. <sf...@ol...>]

OpenGLEAN 0.4.1 has just been released.  See the files section of the
SourceForge page for information.  Fingerprints for the files are:

 (General source tarball; ready to build by hand!)
MD5 (openglean-0.4.1.tar.bz2) = 6018f3a3f143434de0651cb3367950e2
SHA1 (openglean-0.4.1.tar.bz2) = 9693d23681a43a803d9981ba796c37f358139ed1
RMD160 (openglean-0.4.1.tar.bz2) = 3e26754af81dfd9345437db8d19f9225e8278242

 (Pre-built documentation tarball)
MD5 (openglean-0.4.1-doc.tar.bz2) = 9464b2ea2f7c37315a7cfbdac36c3d6e
SHA1 (openglean-0.4.1-doc.tar.bz2) = add4bfa9e97cb0c2788175cee3c5152086e2bb33
RMD160 (openglean-0.4.1-doc.tar.bz2) = 022c12b0047d26aa935b12814db15c49379917fd

 (Platform-independent pkgsrc package; should work on most UNIX-like
  environments, including BSD, GNU/LINUX, Solaris, Interix, ...)
MD5 (OpenGLEAN-pkgsrc-0.4.1.tar.bz2) = cfd82eb81725c69479dddd220e98f9ed
SHA1 (OpenGLEAN-pkgsrc-0.4.1.tar.bz2) = 03ec1099b75513e5e9871a3c2074736210dc0e2d
RMD160 (OpenGLEAN-pkgsrc-0.4.1.tar.bz2) = 3989b5204514e4eeb66399ff42a11fec32aac7c7

 (Pre-built WIN32 .dll and related files; all you need---and perhaps
  then some---to support already-written applications that require
  OpenGLEAN.)
MD5 (OpenGLEAN-win32-0.4.1.zip) = ca5436b78478bd046842538424fd9482
SHA1 (OpenGLEAN-win32-0.4.1.zip) = 2fbb1f091b9cc77abef214d697da93328f8e313c
RMD160 (OpenGLEAN-win32-0.4.1.zip) = 47afa731a6f62abecb90b41ca0dd7bce69ef5dad



Note that several of the more obsolete fingerprint types are no longer
provided.  They do add some security, I suppose, but that is likely to be
marginal.  Including 5 or 6 fingerprint tags per file definitely adds
a lot of clutter, though.

Please NOTE: the WIN32 binaries (OpenGLEAN-win32-0.4.1.zip) should
include everything that you need to use OpenGLEAN (or programs that
require OpenGLEAN).  However, I'm not sure what the minimal subset
is; these files are most of the material that MSVC produces in
the target directory.  Most users will probably only want to
grab the DLL file in the Release directory.  The upshot is that
the binary-only archive for WIN32 is much larger than one might
expect.

-- 
  "I probably don't know what I'm talking about."  http://www.olib.org/~rkr/