mirror of
https://github.com/void-linux/void-packages.git
synced 2025-06-07 15:43:49 +02:00
gtk+3: update to 3.22.26. (#8988)
This commit is contained in:
maxice8
Juan RP
parent
5bed0d462a
commit
d29d5f347b
2 changed files with 2 additions and 101 deletions
|
|
@ -1,95 +0,0 @@
|
||||||
<?xml version="1.0" encoding="UTF-8"?>
|
|
||||||
<protocol name="server_decoration">
|
|
||||||
<copyright><![CDATA[
|
|
||||||
Copyright (C) 2015 Martin Gräßlin
|
|
||||||
|
|
||||||
This program is free software: you can redistribute it and/or modify
|
|
||||||
it under the terms of the GNU Lesser General Public License as published by
|
|
||||||
the Free Software Foundation, either version 2.1 of the License, or
|
|
||||||
(at your option) any later version.
|
|
||||||
|
|
||||||
This program is distributed in the hope that it will be useful,
|
|
||||||
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
||||||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
||||||
GNU Lesser General Public License for more details.
|
|
||||||
|
|
||||||
You should have received a copy of the GNU Lesser General Public License
|
|
||||||
along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
||||||
]]></copyright>
|
|
||||||
<interface name="org_kde_kwin_server_decoration_manager" version="1">
|
|
||||||
<description summary="Server side window decoration manager">
|
|
||||||
This interface allows to coordinate whether the server should create
|
|
||||||
a server-side window decoration around a wl_surface representing a
|
|
||||||
shell surface (wl_shell_surface or similar). By announcing support
|
|
||||||
for this interface the server indicates that it supports server
|
|
||||||
side decorations.
|
|
||||||
</description>
|
|
||||||
<request name="create">
|
|
||||||
<description summary="Create a server-side decoration object for a given surface">
|
|
||||||
When a client creates a server-side decoration object it indicates
|
|
||||||
that it supports the protocol. The client is supposed to tell the
|
|
||||||
server whether it wants server-side decorations or will provide
|
|
||||||
client-side decorations.
|
|
||||||
|
|
||||||
If the client does not create a server-side decoration object for
|
|
||||||
a surface the server interprets this as lack of support for this
|
|
||||||
protocol and considers it as client-side decorated. Nevertheless a
|
|
||||||
client-side decorated surface should use this protocol to indicate
|
|
||||||
to the server that it does not want a server-side deco.
|
|
||||||
</description>
|
|
||||||
<arg name="id" type="new_id" interface="org_kde_kwin_server_decoration"/>
|
|
||||||
<arg name="surface" type="object" interface="wl_surface"/>
|
|
||||||
</request>
|
|
||||||
<enum name="mode">
|
|
||||||
<description summary="Possible values to use in request_mode and the event mode."/>
|
|
||||||
<entry name="None" value="0" summary="Undecorated: The surface is not decorated at all, neither server nor client-side. An example is a popup surface which should not be decorated."/>
|
|
||||||
<entry name="Client" value="1" summary="Client-side decoration: The decoration is part of the surface and the client."/>
|
|
||||||
<entry name="Server" value="2" summary="Server-side decoration: The server embeds the surface into a decoration frame."/>
|
|
||||||
</enum>
|
|
||||||
<event name="default_mode">
|
|
||||||
<description summary="The default mode used on the server">
|
|
||||||
This event is emitted directly after binding the interface. It contains
|
|
||||||
the default mode for the decoration. When a new server decoration object
|
|
||||||
is created this new object will be in the default mode until the first
|
|
||||||
request_mode is requested.
|
|
||||||
|
|
||||||
The server may change the default mode at any time.
|
|
||||||
</description>
|
|
||||||
<arg name="mode" type="uint" summary="The default decoration mode applied to newly created server decorations."/>
|
|
||||||
</event>
|
|
||||||
</interface>
|
|
||||||
<interface name="org_kde_kwin_server_decoration" version="1">
|
|
||||||
<request name="release" type="destructor">
|
|
||||||
<description summary="release the server decoration object"/>
|
|
||||||
</request>
|
|
||||||
<enum name="mode">
|
|
||||||
<description summary="Possible values to use in request_mode and the event mode."/>
|
|
||||||
<entry name="None" value="0" summary="Undecorated: The surface is not decorated at all, neither server nor client-side. An example is a popup surface which should not be decorated."/>
|
|
||||||
<entry name="Client" value="1" summary="Client-side decoration: The decoration is part of the surface and the client."/>
|
|
||||||
<entry name="Server" value="2" summary="Server-side decoration: The server embeds the surface into a decoration frame."/>
|
|
||||||
</enum>
|
|
||||||
<request name="request_mode">
|
|
||||||
<description summary="The decoration mode the surface wants to use."/>
|
|
||||||
<arg name="mode" type="uint" summary="The mode this surface wants to use."/>
|
|
||||||
</request>
|
|
||||||
<event name="mode">
|
|
||||||
<description summary="The new decoration mode applied by the server">
|
|
||||||
This event is emitted directly after the decoration is created and
|
|
||||||
represents the base decoration policy by the server. E.g. a server
|
|
||||||
which wants all surfaces to be client-side decorated will send Client,
|
|
||||||
a server which wants server-side decoration will send Server.
|
|
||||||
|
|
||||||
The client can request a different mode through the decoration request.
|
|
||||||
The server will acknowledge this by another event with the same mode. So
|
|
||||||
even if a server prefers server-side decoration it's possible to force a
|
|
||||||
client-side decoration.
|
|
||||||
|
|
||||||
The server may emit this event at any time. In this case the client can
|
|
||||||
again request a different mode. It's the responsibility of the server to
|
|
||||||
prevent a feedback loop.
|
|
||||||
</description>
|
|
||||||
<arg name="mode" type="uint" summary="The decoration mode applied to the surface by the server."/>
|
|
||||||
</event>
|
|
||||||
</interface>
|
|
||||||
</protocol>
|
|
||||||
|
|
||||||
|
|
@ -1,6 +1,6 @@
|
||||||
# Template build file for 'gtk+3'.
|
# Template build file for 'gtk+3'.
|
||||||
pkgname=gtk+3
|
pkgname=gtk+3
|
||||||
version=3.22.25
|
version=3.22.26
|
||||||
revision=1
|
revision=1
|
||||||
wrksrc="gtk+-${version}"
|
wrksrc="gtk+-${version}"
|
||||||
build_style=gnu-configure
|
build_style=gnu-configure
|
||||||
|
|
@ -13,7 +13,7 @@ maintainer="Juan RP <xtraeme@voidlinux.eu>"
|
||||||
homepage="https://www.gtk.org/"
|
homepage="https://www.gtk.org/"
|
||||||
license="LGPL-2.1"
|
license="LGPL-2.1"
|
||||||
distfiles="${GNOME_SITE}/gtk+/${version%.*}/gtk+-${version}.tar.xz"
|
distfiles="${GNOME_SITE}/gtk+/${version%.*}/gtk+-${version}.tar.xz"
|
||||||
checksum=e25eaed5ab0775ddc211898fbfdc873b19e4a7ab03c0dbe88dff1938b433739e
|
checksum=61eef0d320e541976e2dfe445729f12b5ade53050ee9de6184235cb60cd4b967
|
||||||
|
|
||||||
hostmakedepends="automake gettext-devel libtool pkg-config
|
hostmakedepends="automake gettext-devel libtool pkg-config
|
||||||
glib-devel gtk-doc gobject-introspection gtk-update-icon-cache
|
glib-devel gtk-doc gobject-introspection gtk-update-icon-cache
|
||||||
|
|
@ -43,10 +43,6 @@ pre_configure() {
|
||||||
sed -i 's,pkg-config,/usr/bin/pkg-config,' autogen.sh
|
sed -i 's,pkg-config,/usr/bin/pkg-config,' autogen.sh
|
||||||
NOCONFIGURE=1 ./autogen.sh
|
NOCONFIGURE=1 ./autogen.sh
|
||||||
}
|
}
|
||||||
pre_build() {
|
|
||||||
# see https://bugzilla.gnome.org/show_bug.cgi?id=789630
|
|
||||||
cp "${FILESDIR}"/server-decoration.xml "${wrksrc}"/gdk/wayland/protocol/server-decoration.xml
|
|
||||||
}
|
|
||||||
post_install() {
|
post_install() {
|
||||||
rm -f ${DESTDIR}/usr/bin/gtk-update-icon-cache
|
rm -f ${DESTDIR}/usr/bin/gtk-update-icon-cache
|
||||||
rm -f ${DESTDIR}/usr/share/man/man1/gtk-update-icon-cache.1
|
rm -f ${DESTDIR}/usr/share/man/man1/gtk-update-icon-cache.1
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue