[pkgsrc/trunk]: pkgsrc/wm/ctwm ctwm: update to 4.0.2

[maya <maya%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/c81764eba6ce
branches:  trunk
changeset: 385381:c81764eba6ce
user:      maya <maya%pkgsrc.org@localhost>
date:      Sat Sep 22 07:00:38 2018 +0000

description:
ctwm: update to 4.0.2

>From Rhialto (maintainer) in PR pkg/53584

4.0.2 (2018-08-25)

Backward-Incompatible Changes And Removed Features

-   The UseThreeDIconBorders config var has been removed. It came in
    silently and undocumented in 3.4 and has never done anything.

-   The attempts to use DNS lookups for setting the HOSTNAME m4 variable
    have been removed; it is now just a duplicate of CLIENTHOST.

New Features

-   The EWMH _NET_WM_NAME property is now supported, and used for the
    window name in place of the ICCCM WM_NAME when set. By default, we
    also accept UTF8_STRING encoded WM_NAME as a result of this change;
    see below for var to restore historical strictness.

-   The EWMH _NET_WM_ICON_NAME property is now supported, and used for
    the icon name in place of the ICCCM WM_ICON_NAME when set. Similar
    comments as above apply to the encodings.

-   Support has been added for CTWM_WM_NAME and CTWM_WM_ICON_NAME
    properties, which will override any window/icon names otherwise
    specified. This may be useful for applications that set unhelpful
    names themselves, or for manually adjusting labelling. These
    properties can be set from the command line via xprop; as an
    example, xprop -f CTWM_WM_NAME 8u -set CTWM_WM_NAME "awesome
    windowsauce". See xprop(1) manual for details; the s, t, and u field
    type specifiers will all work.

-   When no icon name is set for a window, we've always used the window
    name for the icon name as well. But that only happened the first
    time the window name is set; after that, the icon name is stuck at
    the first name.  It now updates along with the window name, if no
    icon name is set.

-   All icon manager windows will now have the TwmIconManager class set
    on them, so they can be addressed en mass by other config like
    NoTitle by that class name.

New Config Options

-   Added DontNameDecorations config option to disable setting names on
    the X windows we create for window decoration (added in 4.0.0).
    These have been reported to confuse xwit, and might do the same for
    other tools that don't expect to find them on non-end-app windows.
    Reported by Frank Steiner.

-   Added StrictWinNameEncoding config option to enable historical
    behavior, where we're reject invalid property encoding for window
    naming properties (like a UTF8_STRING encoded WM_NAME).

Bugfixes

-   Fix up broken parsing of IconifyStyle "sweep". Bug was introduced in
    4.0.0.

-   When multiple X Screens are used, building the temporary file for m4
    definitions could fail with an error from mkstemp(). Reported by
    Manfred Knick.

-   When multiple X Screens are used, the OTP code didn't recognize the
    difference, and kept everything in one list. This caused the
    internal consistency checks to trip when it didn't find all the
    windows it expected. Reported by Terran Melconian.

-   When ReverseCurrentWorkspace is set, mapping windows not on the
    current workspace (e.g., via restarting ctwm, or creating new
    windows with the desktop set via EWMH properties) could segfault.
    Reported by Sean McAllister.

-   Fix some edge cases where we'd fight other apps' focus handling.
    When an application moved focus itself to an unrelated (in X terms)
    window, our processing would often race and re-move the focus to the
    root ourselves.  This was visible with e.g. sub-windows in Firefox
    for context menu and urlbar dropdown, which would flash on and then
    disappear.

-   When creating a new transient window of an existing full-screen
    window, the OTP stacking may cause it to be stuck below the main
    window due to the special handling of full-screen focused windows in
    EWMH. It should now be forced to the top.

-   Building ctwm since 4.0.0 in certain locales could misorder
    functions in the lookup table, leading to troubles parsing the
    config file. You'd get some loud "INTERNAL ERROR" lines from ctwm
    when running it if this were the case. Now fixed. Reported by
    Richard Levitte.

diffstat:

 wm/ctwm/Makefile |   4 ++--
 wm/ctwm/distinfo |  10 +++++-----
 2 files changed, 7 insertions(+), 7 deletions(-)

diffs (28 lines):

diff -r e0974b773709 -r c81764eba6ce wm/ctwm/Makefile
--- a/wm/ctwm/Makefile  Sat Sep 22 06:32:11 2018 +0000
+++ b/wm/ctwm/Makefile  Sat Sep 22 07:00:38 2018 +0000
@@ -1,7 +1,7 @@
-# $NetBSD: Makefile,v 1.35 2018/07/14 15:03:42 maya Exp $
+# $NetBSD: Makefile,v 1.36 2018/09/22 07:00:38 maya Exp $
 #
 
-DISTNAME=      ctwm-4.0.1
+DISTNAME=      ctwm-4.0.2
 CATEGORIES=    x11 wm
 MASTER_SITES=  http://ctwm.org/dist/
 EXTRACT_SUFX=  .tar.xz
diff -r e0974b773709 -r c81764eba6ce wm/ctwm/distinfo
--- a/wm/ctwm/distinfo  Sat Sep 22 06:32:11 2018 +0000
+++ b/wm/ctwm/distinfo  Sat Sep 22 07:00:38 2018 +0000
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.19 2018/07/14 15:03:42 maya Exp $
+$NetBSD: distinfo,v 1.20 2018/09/22 07:00:38 maya Exp $
 
-SHA1 (ctwm-4.0.1.tar.xz) = f3bbab93bba124a19ee83fd291a928650fa7ea4b
-RMD160 (ctwm-4.0.1.tar.xz) = 1222c47de9adf430af4719e75fec8d8265e110e7
-SHA512 (ctwm-4.0.1.tar.xz) = 8c5c0bf868ba36cf5acca1ac5dbcea9327f63892698ace5086fabe563632acbb578cefea44ac3de91dc15afdbdce0370169e14156525507b90dc8aca8d305bc6
-Size (ctwm-4.0.1.tar.xz) = 656776 bytes
+SHA1 (ctwm-4.0.2.tar.xz) = e5768bf6c242441aff9a96290840d4e2647cb4ed
+RMD160 (ctwm-4.0.2.tar.xz) = 6de49077a321162223ca80bde9074f91ed951a7f
+SHA512 (ctwm-4.0.2.tar.xz) = 445151f12084acd44bcf8a7d895e29363411a1a663b93e098fa9db5b96ae5cb43921eaf0695026aff2196117b810b96712a60570f57d6dabbee7fba34d5bd57f
+Size (ctwm-4.0.2.tar.xz) = 672608 bytes