Uploaded moonlight 0.5.3-1 (m68k) to erlangen
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.5
Date: Fri, 9 Oct 1998 12:26:26 -0600
Source: moonlight
Binary: moonlight
Architecture: m68k
Version: 0.5.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon <buildd@m68k.debian.org>
Description:
moonlight - create and render 3d scenes
Changes:
moonlight (0.5.3-1) unstable; urgency=low
.
* New upstream version (sorry about the delay, first it was the C++
compiler which didn't like the code, then I had to wait for the new
freetype to make its way into Debian, then MLC crashed right after
starting up and yesterday I finally got it to compile and ran fine,
but lintian complained soundly about a number of warnings and errors)
* Added /usr/X11R6/lib and /usr/X11R6/include to the search paths for
libs and includes (Mesa). Sent upstream.
* added $(DESTDIR) to the install-* targets. Sent upstream.
* applied libtool patches to get -rpath out of the way (modified
debian/rules to patch libtool after configure)
* src/kernel/MLKernelConfig.C: patched to use the value of sysconfdir;
made necessary modifications to configure.in. Sent upstream.
* debian/rules: removes TrueType fonts installed in moonlight's
database; moved the supplied fonts to /usr/share/fonts/truetype/;
modifies TTFontPath in /etc/moonlightrc on binary target.
* Wrote a wrapper script to deal with plug-ins (upstream uses -rpath,
and that "solves" the problem, also, /usr/lib/moonlight is hardcoded
into the binary). Mmmm... I'll have to look into this later, why are
the plug-ins linked with the binary if they are going to be loaded
later?
* Plain Text doesn't work. Looked into that, but it's a bit more complex
than what I initially thought.
* debian/control: changed maintainer information
Files:
a4c063f090673369f0d8573f4ca1bc5f 1432100 graphics optional moonlight_0.5.3-1_m68k.deb
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
iQCVAwUBNjBqw3VhJ0HiWnvJAQF2yAP+J5W99B0FriMmMri3eU5be1BnFP6cpeoQ
81PUiCF5BU70yvwKTKYqQxFgL3Zr3WhXoYJccty5eLWhvJ3iAa8XmBbBlmWx9J5F
STOP/xRrDsgCeUtWztok5rz7+J5AiTqSYBzynwQcXMCSUICvCpcxDBQ50DQST7sJ
mp+VU2ft1Bk=
=3I3E
-----END PGP SIGNATURE-----
Reply to: