Source: wayland
Section: x11
Priority: optional
Maintainer: linuxmangaka <linuxmangaka@gmail.com>
Rules-Requires-Root: no
Build-Depends: debhelper (>= 10),
 libexpat1-dev,
 libffi-dev,
 libwayland-bin <cross>,
 libxml2-dev,
 meson,
 ninja-build,
 pkgconf,
 pkg-config,
 quilt,
Build-Depends-Indep: docbook-xsl,
 doxygen,
 graphviz,
 xmlto,
 xsltproc,
Standards-Version: 4.6.2
Homepage: https://wayland.freedesktop.org/
Vcs-Browser: https://salsa.debian.org/xorg-team/wayland/wayland
Vcs-Git: https://salsa.debian.org/xorg-team/wayland/wayland.git

Package: libwayland-client0
Section: libs
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Replaces: libwayland0 (<< 1.1.0-1),
Conflicts: libwayland0 (<< 1.1.0-1),
Description: Core Wayland window system code and protocol
 Wayland is a project to define a protocol for a compositor to talk to its clients as well as a library implementation of the protocol.  The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself.  The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers. The wayland protocol is essentially only about input handling and buffer management.  The compositor receives input events and forwards them to the relevant client.  The clients creates buffers and renders into them and notifies the compositor when it needs to redraw.  The protocol also handles drag and drop, selections, window management and other interactions that must go through the compositor.  However, the protocol does not handle rendering, which is one of the features that makes wayland so simple.  All clients are expected to handle rendering themselves, typically through cairo or OpenGL.

Package: libwayland-egl1
Section: libs
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Provides: libwayland-egl1-mesa,
Breaks: libwayland-egl1-mesa (<< 18.0.5-0),
Replaces: libwayland-egl1-mesa (<< 18.0.5-0),
Description: Core Wayland window system code and protocol
 Wayland is a project to define a protocol for a compositor to talk to its clients as well as a library implementation of the protocol.  The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself.  The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers. The wayland protocol is essentially only about input handling and buffer management.  The compositor receives input events and forwards them to the relevant client.  The clients creates buffers and renders into them and notifies the compositor when it needs to redraw.  The protocol also handles drag and drop, selections, window management and other interactions that must go through the compositor.  However, the protocol does not handle rendering, which is one of the features that makes wayland so simple.  All clients are expected to handle rendering themselves, typically through cairo or OpenGL.

Package: libwayland-server0
Section: libs
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: weston (<< 1.2.0),
Replaces: libwayland0 (<< 1.1.0-1),
Conflicts: libwayland0 (<< 1.1.0-1),
Description: Core Wayland window system code and protocol
 Wayland is a project to define a protocol for a compositor to talk to its clients as well as a library implementation of the protocol.  The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself.  The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers. The wayland protocol is essentially only about input handling and buffer management.  The compositor receives input events and forwards them to the relevant client.  The clients creates buffers and renders into them and notifies the compositor when it needs to redraw.  The protocol also handles drag and drop, selections, window management and other interactions that must go through the compositor.  However, the protocol does not handle rendering, which is one of the features that makes wayland so simple.  All clients are expected to handle rendering themselves, typically through cairo or OpenGL.

Package: libwayland-cursor0
Section: libs
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Conflicts: libwayland0 (<< 1.1.0-1),
Replaces: libwayland0 (<< 1.1.0-1),
Description: Core Wayland window system code and protocol
 Wayland is a project to define a protocol for a compositor to talk to its clients as well as a library implementation of the protocol.  The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself.  The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers. The wayland protocol is essentially only about input handling and buffer management.  The compositor receives input events and forwards them to the relevant client.  The clients creates buffers and renders into them and notifies the compositor when it needs to redraw.  The protocol also handles drag and drop, selections, window management and other interactions that must go through the compositor.  However, the protocol does not handle rendering, which is one of the features that makes wayland so simple.  All clients are expected to handle rendering themselves, typically through cairo or OpenGL.

Package: libwayland-dev
Section: libdevel
Architecture: any
Suggests: libwayland-doc
Multi-Arch: same
Depends: ${shlibs:Depends},
 ${misc:Depends},
 libwayland-bin (= ${binary:Version}),
 libwayland-client0 (= ${binary:Version}),
 libwayland-cursor0 (= ${binary:Version}),
 libwayland-egl1 (= ${binary:Version}),
 libwayland-server0 (= ${binary:Version}),
 libffi-dev,
Breaks: libegl1-mesa-dev (<< 18.0.5-0),
Replaces: libegl1-mesa-dev (<< 18.0.5-0),
Description: Core Wayland window system code and protocol
 Wayland is a project to define a protocol for a compositor to talk to its clients as well as a library implementation of the protocol.  The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself.  The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers. The wayland protocol is essentially only about input handling and buffer management.  The compositor receives input events and forwards them to the relevant client.  The clients creates buffers and renders into them and notifies the compositor when it needs to redraw.  The protocol also handles drag and drop, selections, window management and other interactions that must go through the compositor.  However, the protocol does not handle rendering, which is one of the features that makes wayland so simple.  All clients are expected to handle rendering themselves, typically through cairo or OpenGL.

Package: libwayland-egl-backend-dev
Section: libdevel
Architecture: any
Multi-Arch: same
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libegl1-mesa-dev (<< 18.0.5-0),
 libwayland-dev (<< 1.15.0),
Replaces: libegl1-mesa-dev (<< 18.0.5-0),
 libwayland-dev (<< 1.15.0),
Description: Core Wayland window system code and protocol
 Wayland is a project to define a protocol for a compositor to talk to its clients as well as a library implementation of the protocol.  The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself.  The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers. The wayland protocol is essentially only about input handling and buffer management.  The compositor receives input events and forwards them to the relevant client.  The clients creates buffers and renders into them and notifies the compositor when it needs to redraw.  The protocol also handles drag and drop, selections, window management and other interactions that must go through the compositor.  However, the protocol does not handle rendering, which is one of the features that makes wayland so simple.  All clients are expected to handle rendering themselves, typically through cairo or OpenGL.

Package: libwayland-doc
Section: doc
Architecture: all
Multi-Arch: foreign
Depends: ${shlibs:Depends},
 ${misc:Depends},
Conflicts: libwayland-dev (<< 1.10.0-2),
Replaces: libwayland-dev (<< 1.10.0-2),
Description: Core Wayland window system code and protocol
 Wayland is a project to define a protocol for a compositor to talk to its clients as well as a library implementation of the protocol.  The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself.  The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers. The wayland protocol is essentially only about input handling and buffer management.  The compositor receives input events and forwards them to the relevant client.  The clients creates buffers and renders into them and notifies the compositor when it needs to redraw.  The protocol also handles drag and drop, selections, window management and other interactions that must go through the compositor.  However, the protocol does not handle rendering, which is one of the features that makes wayland so simple.  All clients are expected to handle rendering themselves, typically through cairo or OpenGL.

Package: libwayland-bin
Section: libdevel
Architecture: any
Multi-Arch: foreign
Depends: ${shlibs:Depends},
 ${misc:Depends},
Conflicts: libwayland-dev (<< 1.11.0-1),
Replaces: libwayland-dev (<< 1.11.0-1),
Description: Core Wayland window system code and protocol
 Wayland is a project to define a protocol for a compositor to talk to its clients as well as a library implementation of the protocol.  The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself.  The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers. The wayland protocol is essentially only about input handling and buffer management.  The compositor receives input events and forwards them to the relevant client.  The clients creates buffers and renders into them and notifies the compositor when it needs to redraw.  The protocol also handles drag and drop, selections, window management and other interactions that must go through the compositor.  However, the protocol does not handle rendering, which is one of the features that makes wayland so simple.  All clients are expected to handle rendering themselves, typically through cairo or OpenGL.