wayland-1.10.0

[Fernando de Oliveira]

​http://wayland.freedesktop.org/releases/wayland-1.10.0.tar.xz

​http://wayland.freedesktop.org/releases/wayland-1.10.0.tar.xz.sig

​https://lists.freedesktop.org/archives/wayland-devel/2016-February/027038.html

MD5: e7751c38807c231afaba9d6b68f2a2b7 wayland-1.10.0.tar.xz

[ANNOUNCE] wayland 1.10.0
Bryce Harrington bryce at osg.samsung.com
Wed Feb 17 00:11:46 UTC 2016

Welcome to the Wayland 1.10 release!  This is a big release with a bunch
of new functionality:

Drag and drop actions are now added to the Wayland API, to facilitate
negotiation of content type when dragging between a source and
destination, and provision is made to communicate the completion (or
cancellation) of the drag action back to the source.  This is designed a
bit differently than the XDND protocol in X11, in that the drag
destination is allowed more control to decide the action to use.

Frame events group pointer events together, to allow things like
diagonal scrolling (which combines horizontal and vertical scroll
events).  New events are also added to more precisely track wheel click
counts, termination of scroll sequences, and how axis events were
generated.

A buffer damage request, wl_surface.damage_buffer, allows applications
a more convenient way to communicate portions of a surface needing to be
re-rendered.

Shared memory buffers now do reference counting to allow compositors to
delay releasing the memory pools until they're no longer in use.
Enlightenment uses this for doing asynchronous rendering.

There are now provisions for deleting wl_seat objects.  This is useful
in compositors that handle multiple seats such as for remote desktops.

Specific version numbers can be associated with protocol objects
client-side.  For backwards compatibility, version 0 is recognized as
indicating an unversioned API.

New APIs are provided for getting and setting the socket file descriptor
Wayland servers use to communicate with their clients.  This
functionality can be used in SELinux or SMACK environments for improved
security.

This release introduces the enum and bitfield attributes, which allow
protocol designers to refer to the specific enum that is expected in an
argument.  Enums can also be specified as bitfields, as opposed to just
ordinary numerical sequences.

Quite a few clarifications to protocols and API are added;
many of these arose as various desktop environments implemented their
own Wayland support.  And of course a rich assortment of bug fixes, code
cleanups, and test code enhancements are included.  Of particular note,
the scanner now validates the protocol XML using a wayland.dtd.

See also my blog post with a bit more discussion:

  http://blogs.s-osg.org/whats-new-wayland-1-10/


Next Release:
-------------
Here is a proposed schedule for the 1.11 release cycle:

  - Development of the 1.11 cycle starts immediately.

  - 1.11-alpha around May 3rd.  Major features done by this point.

  - 1.11-beta around May 17th.

  - 1.11-rc1 around May 24th.

  - 1.11.0 release around May 31st.

Perhaps we can target a 1.12.0 in late August, and squeeze in a 1.13
before the end of the year.


Changes since 1.9.93:
---------------------

    Bryce Harrington (1):
      configure.ac: bump to version 1.10.0 for the official release

    Jonas Ådahl (1):
      connection: Don't add uninitialized memory as 4 byte alignment padding


Full Changes since 1.9.0
------------------------

    Auke Booij (5):
      Remove protocol/wayland.dtd
      doc: document the enum and bitfield attributes
      protocol: specify enum and bitfield attributes
      scanner: enforce correct argument type for enums
      doc: output enum and bitfield attributes in the documentation

    Bryce Harrington (10):
      configure.ac: bump to version 1.9.90 for open development
      scanner: Close input resource when done to prevent leak
      server: Add a socket with an existing fd
      socket-test: Fix some comment typos
      socket-test: Refactor if check into the assert
      configure.ac: bump to version 1.9.91 for the alpha release
      configure.ac: re-bump to version 1.9.91 for the alpha release
      configure.ac: bump to version 1.9.92 for the beta release
      configure.ac: bump to version 1.9.93 for the RC1 release
      configure.ac: bump to version 1.10.0 for the official release

    Carlos Garnacho (2):
      protocol: Improve data source notification around DnD progress
      protocol: Add DnD actions

    Derek Foreman (11):
      shm: Add shm_buffer ref and shm_pool unref functions
      shm: Deprecate wl_shm_buffer_create()
      shm: Move deprecated function to the bottom of the file
      shm: wl_shm_buffer_get_data() requires a valid pool.
      protocol: Remove incorrect statement that attach must precede damage
      protocol: Add wl_surface.damage_buffer
      server: improve failure log message for wl_global_create()
      server: Test for illegally low interface versions in wl_global_create()
      tests: Test proxy versions
      server: Fail to bind object when requested version is 0
      scanner: Fix oddities in copyright printing

    FORT David (1):
      wayland: add a release request on wl_seat

    Jaeyoon Jung (1):
      server: Calculate remaining data size after a closure is processed

    Jason Ekstrand (1):
      Track protocol object versions inside wl_proxy.

    Jon Cruz (3):
      cosmetic: fix inconsistent code style with header prototypes.
      scanner: stop adding trailing whitespace to copyright
      cosmetic: fix incorrect whitespace.

    Jonas Ådahl (22):
      client: Fix minor grammar issue
      client: Reword and add documentation about the marshal functions
      client: Be more clear about when one must call wl_display_flush
      client: Improve wl_display_roundtrip(_queue)() documentation
      client: Move prepare read documentation to .._prepare_read_queue()
      scanner: Generate 'since' macros for requests as well
      scanner: Add missing brackets
      scanner: Fail if 'since' is higher than the interface version
      Use zalloc instead of malloc + memset
      doc: Fix function membership
      doc: Fix incorrect parameter name
      client: Correct documentation regarding thread safeness
      client: Remove misplaced documentation about main loop intergration
      client: Don't make EPIPE fatal if triggered when flushing
      client: Use read preparation API in wl_display_dispatch_queue()
      client: Fully flush during blocking dispatch
      tests: Synchronize client termination in idle callback
      tests: Pass argument to client main
      tests: Test that one can fetch the protocol error after EPIPE
      protocol: Add note about per version requirements to wl_data_device_manager
      scanner: Print filename on DTD validation error
      connection: Don't add uninitialized memory as 4 byte alignment padding

    Marek Chalupa (5):
      event-loop: remove extra header
      add wl_abort private function
      server: remove redundant include
      server: don't send an error to NULL display_resource
      cosmetic: return NULL instead of 0

    Pekka Paalanen (3):
      Contributing: explain Patchwork
      Makefile: use automake rule for compiling .S
      scanner: drop altmacro from dtddata.S

    Peter Hutterer (8):
      doc: make the doxygen output dependent on scanner.c
      Revert "Remove protocol/wayland.dtd"
      protocol: allow for a <description> element below <protocol>
      protocol: add the new bitfields to the dtd
      Validate the protocol xml during scanning
      protocol: fix a couple of whitespace issues
      protocol: specify behavior of get_pointer when capabilities change
      protocol: add wl_pointer.frame, axis_source, axis_stop, and axis_discrete

    Sergi Granell (3):
      server: Fix possible wl_display_add_socket_fd memleak
      cosmetic: use tabs instead of spaces
      cosmetic: add an space after if

    Sung-Jin Park (1):
      server: Add an API to get the file descriptor for a client

    Victor Berger (1):
      client: Add missing arg in a wl_log invocation

[ken@…]

I'll see if this lets Mesa build, and if so I'll put it in 7.9

Of course the real test will come whenever somebody gets to kf5 and plasma.

[ken@…]

Gave it a go with the versions of kf5 and plasma that are currently in the book : all build ok.

[ken@…]

r16985