Uploaded wmaker 0.65.0-3 (m68k) to erlangen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 16 Jun 2001 20:29:16 +0200
Source: wmaker
Binary: libwraster2-dev libwmaker0-dev wmaker libwings-dev libwraster2
Architecture: m68k
Version: 0.65.0-3
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon <buildd@kullervo.biophys.uni-duesseldorf.de>
Changed-By: Marcelo E. Magallon <mmagallo@debian.org>
Description:
libwings-dev - Window Maker's own widget set
libwmaker0-dev - Static libraries and headers for Window Maker applications.
libwraster2 - Shared libraries of Window Maker rasterizer.
libwraster2-dev - Static libraries and headers of Window Maker rasterizer.
wmaker - NeXTSTEP-like window manager for X
Changes:
wmaker (0.65.0-3) unstable; urgency=low
.
* Use upstream's patch for bug#99311
* Kill window instance numbers. This feature drives all the Window Maker
users I know up the wall.
* src/wconfig.h.in: cheat regarding the dissapearing WorkSpace name.
Window Maker is compiled with I18N, which makes LargeDisplayFont
-*-*-medium-r-normal--24-*, which, with some combination of font
pakcages, selects some non 8859-1 font, which means nothing is
displayed. Changing this to -*-*-bold-r-normal--24-* makes the Xserver
(?) pick something else. Someone with a clue regarding MB please help.
Files:
5fb84a3b8c01dc75798b3eeccbe0a5c7 1781294 x11 optional wmaker_0.65.0-3_m68k.deb
82fd8bc8aa5dfa160e45c23d1e539d4b 55234 devel optional libwmaker0-dev_0.65.0-3_m68k.deb
931c7d2a1fbd6121c63fbd49898e8924 93974 devel optional libwraster2-dev_0.65.0-3_m68k.deb
9ac37e51df0cfbe5d03b645bf7461c2c 87510 libs optional libwraster2_0.65.0-3_m68k.deb
78c569dc733f40bf6771236f3acb7b7f 264702 devel optional libwings-dev_0.65.0-3_m68k.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/>
iEYEARECAAYFAjsvCq4ACgkQcS3JWD3Fdvd0owCeMXoX+I9cSDuzOyQt6BCjSYdV
jjkAni9vTVhjKernZKShqGOt+4+yz1hq
=NVOf
-----END PGP SIGNATURE-----
Reply to: