Hello community, here is the log from the commit of package kwayland for openSUSE:Factory checked in at 2018-05-18 14:24:06 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/kwayland (Old) and /work/SRC/openSUSE:Factory/.kwayland.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "kwayland" Fri May 18 14:24:06 2018 rev:49 rq:607591 version:5.46.0 Changes: -------- --- /work/SRC/openSUSE:Factory/kwayland/kwayland.changes 2018-04-19 15:18:58.952581029 +0200 +++ /work/SRC/openSUSE:Factory/.kwayland.new/kwayland.changes 2018-05-18 14:24:10.806568751 +0200 @@ -1,0 +2,10 @@ +Sun May 13 21:03:07 UTC 2018 - [email protected] + +- Update to 5.46.0 + * New feature release + * For more details please see: + * https://www.kde.org/announcements/kde-frameworks-5.46.0.php +- Changes since 5.45.0: + * Improve protocols documentation + +------------------------------------------------------------------- Old: ---- kwayland-5.45.0.tar.xz New: ---- kwayland-5.46.0.tar.xz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ kwayland.spec ++++++ --- /var/tmp/diff_new_pack.nih2sb/_old 2018-05-18 14:24:11.566540857 +0200 +++ /var/tmp/diff_new_pack.nih2sb/_new 2018-05-18 14:24:11.570540710 +0200 @@ -16,13 +16,13 @@ # -%define _tar_path 5.45 +%define _tar_path 5.46 # Full KF5 version (e.g. 5.33.0) %{!?_kf5_version: %global _kf5_version %{version}} # Last major and minor KF5 version (e.g. 5.33) %{!?_kf5_bugfix_version: %global _kf5_bugfix_version %(echo %{_kf5_version} | awk -F. '{print $1"."$2}')} Name: kwayland -Version: 5.45.0 +Version: 5.46.0 Release: 0 Summary: KDE Wayland library License: LGPL-2.1-or-later ++++++ kwayland-5.45.0.tar.xz -> kwayland-5.46.0.tar.xz ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/kwayland-5.45.0/CMakeLists.txt new/kwayland-5.46.0/CMakeLists.txt --- old/kwayland-5.45.0/CMakeLists.txt 2018-04-07 09:48:40.000000000 +0200 +++ new/kwayland-5.46.0/CMakeLists.txt 2018-05-05 14:39:54.000000000 +0200 @@ -1,11 +1,11 @@ cmake_minimum_required(VERSION 3.0) -set(KF5_VERSION "5.45.0") # handled by release scripts +set(KF5_VERSION "5.46.0") # handled by release scripts project(KWayland VERSION ${KF5_VERSION}) # ECM setup include(FeatureSummary) -find_package(ECM 5.45.0 NO_MODULE) +find_package(ECM 5.46.0 NO_MODULE) set_package_properties(ECM PROPERTIES TYPE REQUIRED DESCRIPTION "Extra CMake Modules." URL "https://projects.kde.org/projects/kdesupport/extra-cmake-modules";) feature_summary(WHAT REQUIRED_PACKAGES_NOT_FOUND FATAL_ON_MISSING_REQUIRED_PACKAGES) set(CMAKE_MODULE_PATH ${ECM_MODULE_PATH} ${ECM_KDE_MODULE_DIR}) diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/kwayland-5.45.0/src/client/protocols/output-management.xml new/kwayland-5.46.0/src/client/protocols/output-management.xml --- old/kwayland-5.45.0/src/client/protocols/output-management.xml 2018-04-07 09:48:40.000000000 +0200 +++ new/kwayland-5.46.0/src/client/protocols/output-management.xml 2018-05-05 14:39:54.000000000 +0200 @@ -1,10 +1,10 @@ <?xml version="1.0" encoding="UTF-8"?> <protocol name="outputmanagement"> <copyright><![CDATA[ - Copyright © 2015 Sebastian Kügler <[email protected]> Copyright © 2008-2011 Kristian Høgsberg Copyright © 2010-2011 Intel Corporation Copyright © 2012-2013 Collabora, Ltd. + Copyright © 2015 Sebastian Kügler <[email protected]> Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted @@ -29,81 +29,83 @@ ]]></copyright> <interface name="org_kde_kwin_outputmanagement" version="1"> - <description summary="list connected, but disabled outputs"> - This interface allows to connected output devices for screen configuration purposes. + <description summary="configuration of server outputs through clients"> + This interface enables clients to set properties of output devices for screen + configuration purposes via the server. To this end output devices are referenced + by global org_kde_kwin_outputdevice objects. - OutputManagement (wl_global) + outputmanagement (wl_global) -------------------------- request: - * createConfiguration -> OutputConfiguration (wl_resource) + * create_configuration -> outputconfiguration (wl_resource) - OutputConfiguration (wl_resource) + outputconfiguration (wl_resource) -------------------------- requests: - * enable(output, bool) - * mode(output, mode_id) - * transformation(output, flag) - * position(output, x, y) + * enable(outputdevice, bool) + * mode(outputdevice, mode_id) + * transformation(outputdevice, flag) + * position(outputdevice, x, y) * apply events: * applied * failed - The idea is that we register one OutputManagement as a global. When KScreen - wants to configure it calls createConfiguration which provides a resource - referencing an OutputConfiguration for one-time configuration. That way we can - easily group all requests and know on the server which one belong together. On - the OutputConfiguration it calls for each Output whether it's enabled, which - mode to use (by referencing the mode from the list of announced modes) and the - global position. Once all outputs are configured that way, it calls apply. At - that point and not earlier the server emits a signal to KWin with the complete - wanted configuration which KWin can then try to apply. If that succeeds it - emits the applied signal, otherwise the failed. So even KScreen can know about - it. - - That interface is nicely atomic (as KWin only gets the apply for everything - setup), it solves the 1:n mapping problem: each OutputConfiguration is only a - 1:1 mapping, and we do not need to copy all the requests again by just - referencing a mode id. + The server registers one outputmanagement object as a global object. In order + to configure outputs a client requests create_configuration, which provides a + resource referencing an outputconfiguration for one-time configuration. That + way the server knows which requests belong together and can group them by that. + + On the outputconfiguration object the client calls for each output whether the + output should be enabled, which mode should be set (by referencing the mode from + the list of announced modes) and the output's global position. Once all outputs + are configured that way, the client calls apply. + At that point and not earlier the server should try to apply the configuration. + If this succeeds the server emits the applied signal, otherwise the failed + signal, such that the configuring client is noticed about the success of its + configuration request. + Through this design the interface enables atomic output configuration changes if + internally supported by the server. </description> <request name="create_configuration"> - <description summary="change the shell surface position"> - Request an output configuration, which can be changed and then applied. + <description summary="provide outputconfiguration object for configuring outputs"> + Request an outputconfiguration object through which the client can configure + output devices. </description> <arg name="id" type="new_id" interface="org_kde_kwin_outputconfiguration"/> </request> </interface> - <interface name="org_kde_kwin_outputconfiguration" version="1"> - <description summary="list connected, but disabled outputs"> + <description summary="configure single output devices"> outputconfiguration is a client-specific resource that can be used to ask - the compositor to apply changes to the outputdevices, the monitors connected - to the system. - The client receives a list of outputdevices from the registry. When it wants + the server to apply changes to available output devices. + + The client receives a list of output devices from the registry. When it wants to apply new settings, it creates a configuration object from the outputmanagement global, writes changes through this object's enable, scale, - transform and mode calls. It then asks the compositor to apply these settings - in an atomic fashion, for example through Linux's DRM interface. - The compositor signals back whether the new settings have applied successfully - or failed to apply. outputdevices are updated after the hardware changes have - been applied and before the server side fires applied. + transform and mode calls. It then asks the server to apply these settings in + an atomic fashion, for example through Linux' DRM interface. + + The server signals back whether the new settings have applied successfully + or failed to apply. outputdevice objects are updated after the changes have been + applied to the hardware and before the server side sends the applied event. </description> <request name="enable"> <description summary="enable or disable an output"> Mark the output as enabled or disabled. </description> - <arg name="outputdevice" type="object" interface="org_kde_kwin_outputdevice"/> - <arg name="enable" type="int" summary="request to enable or disable this output"/> + <arg name="outputdevice" type="object" interface="org_kde_kwin_outputdevice" summary="outputdevice to be en- or disabled"/> + <arg name="enable" type="int" summary="1 to enable or 0 to disable this output"/> </request> <request name="mode"> - <description summary="Switch outputdevice to mode"> + <description summary="switch outputdevice to mode"> Sets the mode for a given output by its mode size (width and height) and refresh rate. </description> <arg name="outputdevice" type="object" interface="org_kde_kwin_outputdevice" summary="outputdevice this mode change applies to"/> @@ -111,7 +113,7 @@ </request> <request name="transform"> - <description summary="Transform outputdevice"> + <description summary="transform outputdevice"> Sets the transformation for a given output. </description> <arg name="outputdevice" type="object" interface="org_kde_kwin_outputdevice" summary="outputdevice this transformation change applies to"/> @@ -119,12 +121,14 @@ </request> <request name="position"> - <description summary="Position output relative to global"> - Sets the position for this output device in the global space. position - describes the top-left border of the output in the global space. The - left-most output's top-left border is 0, 0. - There may be no gaps between outputs, the outputs have to be positioned - stacked horizontally, vertically, or both. + <description summary="position output in global space"> + Sets the position for this output device. (x,y) describe the top-left corner + of the output in global space, whereby the origin (0,0) of the global space + has to be aligned with the top-left corner of the most left and in case this + does not define a single one the top output. + + There may be no gaps or overlaps between outputs, i.e. the outputs are + stacked horizontally, vertically, or both on each other. </description> <arg name="outputdevice" type="object" interface="org_kde_kwin_outputdevice" summary="outputdevice this position applies to"/> <arg name="x" type="int" summary="position on the x-axis"/> @@ -132,29 +136,30 @@ </request> <request name="scale"> - <description summary="Set the scaling factor for this outputdevice"> - Sets the scaling factor for this outputdevice. + <description summary="set scaling factor of this output"> + Sets the scaling factor for this output device. </description> <arg name="outputdevice" type="object" interface="org_kde_kwin_outputdevice" summary="outputdevice this mode change applies to"/> <arg name="scale" type="int" summary="scaling factor"/> </request> <request name="apply"> - <description summary="apply the changes to the outputdevices"> - Asks the compositor to apply changes to the outputdevices on the server side. + <description summary="apply configuration changes to all output devices"> + Asks the server to apply property changes requested through this outputconfiguration + object to all outputs on the server side. </description> </request> - <event name="applied"> <description summary="configuration changes have been applied"> - Fired after the compositor has applied the changes successfully. + Sent after the server has successfully applied the changes. + . </description> </event> <event name="failed"> <description summary="configuration changes failed to apply"> - Fired if the compositor rejects or failed to apply the changes. + Sent if the server rejects the changes or failed to apply them. </description> </event> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/kwayland-5.45.0/src/client/protocols/outputdevice.xml new/kwayland-5.46.0/src/client/protocols/outputdevice.xml --- old/kwayland-5.45.0/src/client/protocols/outputdevice.xml 2018-04-07 09:48:40.000000000 +0200 +++ new/kwayland-5.46.0/src/client/protocols/outputdevice.xml 2018-05-05 14:39:54.000000000 +0200 @@ -1,10 +1,10 @@ <?xml version="1.0" encoding="UTF-8"?> <protocol name="org_kde_kwin_outputdevice"> <copyright><![CDATA[ - Copyright © 2015 Sebastian Kügler <[email protected]> Copyright © 2008-2011 Kristian Høgsberg Copyright © 2010-2011 Intel Corporation Copyright © 2012-2013 Collabora, Ltd. + Copyright © 2015 Sebastian Kügler <[email protected]> Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted @@ -30,23 +30,29 @@ <interface name="org_kde_kwin_outputdevice" version="1"> - <description summary="compositor output region"> - An outputdevice describes a physical monitor connected to the system. - outputdevice is similar to wl_output, but focuses on screen - management. The screen configuration client uses outputdevices to - enlist connected devices, even those that may currently not be used - by the compositor as wl_output. It sends configuration changes to the - compositor through the outputconfiguration interface, which applies the - settings to the hardware and signals changes the outputdevices + <description summary="output configuration representation"> + An outputdevice describes a display device available to the compositor. + outputdevice is similar to wl_output, but focuses on output + configuration management. + + A client can query all global outputdevice objects to enlist all + available display devices, even those that may currently not be + represented by the compositor as a wl_output. + + The client sends configuration changes to the server through the + outputconfiguration interface, and the server applies the configuration + changes to the hardware and signals changes to the outputdevices accordingly. - This object is published as global during start up, or when a monitor - is hotplugged. + + This object is published as global during start up for every available + display devcies, or when one later becomes available, for example by + being hotplugged via a physical connector. </description> <enum name="subpixel"> <description summary="subpixel geometry information"> - This enumeration describes how the physical - pixels on an output are laid out. + This enumeration describes how the physical pixels on an output are + laid out. </description> <entry name="unknown" value="0"/> <entry name="none" value="1"/> @@ -58,17 +64,16 @@ <enum name="transform"> <description summary="transform from framebuffer to output"> - This describes the transform that a compositor will apply to a + This describes the transform, that a compositor will apply to a surface to compensate for the rotation or mirroring of an output device. The flipped values correspond to an initial flip around a vertical axis followed by rotation. - The purpose is mainly to allow clients render accordingly and + The purpose is mainly to allow clients to render accordingly and tell the compositor, so that for fullscreen surfaces, the - compositor will still be able to scan out directly from client - surfaces. + compositor is still able to scan out directly client surfaces. </description> <entry name="normal" value="0"/> @@ -82,7 +87,7 @@ </enum> <event name="geometry"> - <description summary="properties of the output"> + <description summary="geometric properties of the output"> The geometry event describes geometric properties of the output. The event is sent when binding to the output object and whenever any of the properties change. @@ -107,8 +112,8 @@ <enum name="mode"> <description summary="mode information"> - These flags describe properties of an output mode. - They are used in the flags bitfield of the mode event. + These flags describe properties of an output mode. They are + used in the flags bitfield of the mode event. </description> <entry name="current" value="0x1" summary="indicates this is the current mode"/> @@ -117,23 +122,28 @@ </enum> <event name="mode"> - <description summary="advertise available modes for the output"> + <description summary="advertise available output modes and current one"> The mode event describes an available mode for the output. - The event is sent when binding to the output object and there - will always be one mode, the current mode. The event is sent - again if an output changes mode, for the mode that is now - current. In other words, the current mode is always the last - mode that was received with the current flag set. - - The size of a mode is given in physical hardware units of - the output device. This is not necessarily the same as - the output size in the global compositor space. For instance, - the output may be scaled, as described in org_kde_kwin_outputdevice.scale, - or transformed , as described in org_kde_kwin_outputdevice.transform. + When the client binds to the outputdevice object, the server sends this + event once for every available mode the outputdevice can be operated by. + + There will always be at least one event sent out on initial binding, + which represents the current mode. + + Later on if an output changes its mode the event is sent again, whereby + this event represents the mode that has now become current. In other + words, the current mode is always represented by the latest event sent + with the current flag set. + + The size of a mode is given in physical hardware units of the output device. + This is not necessarily the same as the output size in the global compositor + space. For instance, the output may be scaled, as described in + org_kde_kwin_outputdevice.scale, or transformed, as described in + org_kde_kwin_outputdevice.transform. - The id can be used to refer to a mode when calling - set_mode on a org_kde_kwin_outputonfiguration. + The id can be used to refer to a mode when calling set_mode on an + org_kde_kwin_outputconfiguration object. </description> <arg name="flags" type="uint" summary="bitfield of mode flags"/> <arg name="width" type="int" summary="width of the mode in hardware units"/> @@ -144,11 +154,11 @@ <event name="done"> <description summary="sent all information about output"> - This event is sent after all other properties has been - sent after binding to the output object and after any - other property changes done after that. This allows - changes to the output properties to be seen as - atomic, even if they happen via multiple events. + This event is sent after all other properties have been + sent on binding to the output object as well as after any + other output property change have been applied later on. + This allows to see changes to the output properties as atomic, + even if multiple events successively announce them. </description> </event> @@ -162,7 +172,7 @@ A scale larger than 1 means that the compositor will automatically scale surface buffers by this amount - when rendering. This is used for very high resolution + when rendering. This is used for high resolution displays where applications rendering at the native resolution would be too small to be legible. @@ -181,7 +191,7 @@ The edid event encapsulates the EDID data for the outputdevice. The event is sent when binding to the output object. The EDID - data may be empty, in which case this event is fired, anyway. + data may be empty, in which case this event is sent anyway. If the EDID information is empty, you can fall back to the name et al. properties of the outputdevice. </description> @@ -189,7 +199,7 @@ </event> <enum name="enablement"> - <description summary="device is used to display content by the compositor"> + <description summary="describes enabled state"> Describes whether a device is enabled, i.e. device is used to display content by the compositor. This wraps a boolean around an int to avoid a boolean trap. @@ -199,22 +209,23 @@ </enum> <event name="enabled"> - <description summary="advertise available modes for the output"> + <description summary="output is enabled or disabled"> The enabled event notifies whether this output is currently - enabled and used for displaying content the wayland server. - The event is sent when binding to the output object, and when - an output is enabled or disabled. + enabled and used for displaying content by the server. + The event is sent when binding to the output object and + whenever later on an output changes its state by becoming + enabled or disabled. </description> - <arg name="enabled" type="int" summary="output is enabled in the wayland server"/> + <arg name="enabled" type="int" summary="output enabled state"/> </event> <event name="uuid"> <description summary="A unique id for this outputdevice"> - The uuid can be used to identify the output. It's controlled by the server entirely. - The compositor should make sure the uuid is persistant across restarts. - An empty uuid is considered invalid. + The uuid can be used to identify the output. It's controlled by + the server entirely. The server should make sure the uuid is + persistant across restarts. An empty uuid is considered invalid. </description> - <arg name="uuid" type="string" summary="Output devices ID"/> + <arg name="uuid" type="string" summary="output devices ID"/> </event>
