---
- branch: MAIN
  date: Tue Aug 27 21:16:03 UTC 2019
  files:
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/kwayland/DESCR
    pathrev: pkgsrc/devel/kwayland/DESCR@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/kwayland/Makefile
    pathrev: pkgsrc/devel/kwayland/Makefile@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/kwayland/PLIST
    pathrev: pkgsrc/devel/kwayland/PLIST@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/kwayland/buildlink3.mk
    pathrev: pkgsrc/devel/kwayland/buildlink3.mk@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/kwayland/distinfo
    pathrev: pkgsrc/devel/kwayland/distinfo@1.1
    type: added
  id: 20190827T211603Z.898d16a406bbc87e84d9277c5db2f9f00688bd03
  log: |
    kwayland: Add version 5.61.0

    KWayland provides two libraries:

    - KWayland::Client
    - KWayland::Server

    As the names suggest they implement a Client respectively a Server API for the Wayland
    protocol. The API is Qt-styled removing the needs to interact with a for a Qt developer
    uncomfortable low-level C-API. For example the callback mechanism from the Wayland API
    is replaced by signals; data types are adjusted to be what a Qt developer expects, e.g.
    two arguments of int are represented by a QPoint or a QSize.
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/devel/kwayland'
  unixtime: '1566940563'
  user: markd