# Buildsheet autogenerated by ravenadm tool -- Do not edit.

NAMEBASE=		python-dbus-python
VERSION=		1.4.0
KEYWORDS=		python
VARIANTS=		v13 v12
SDESC[v12]=		Python bindings for libdbus (3.12)
SDESC[v13]=		Python bindings for libdbus (3.13)
HOMEPAGE=		http://www.freedesktop.org/wiki/Software/DBusBindings/#python
CONTACT=		Python_Automaton[python@ironwolf.systems]

DOWNLOAD_GROUPS=	main
SITES[main]=		PYPI/d/dbus-python
DISTFILE[1]=		dbus-python-1.4.0.tar.gz:main
DIST_SUBDIR=		python-src
DF_INDEX=		1
SPKGS[v12]=		set
			primary
			dev
SPKGS[v13]=		set
			primary
			dev

OPTIONS_AVAILABLE=	PY313 PY312
OPTIONS_STANDARD=	none
VOPTS[v12]=		PY313=OFF PY312=ON
VOPTS[v13]=		PY313=ON PY312=OFF

BUILD_DEPENDS=		dbus:dev:std
BUILDRUN_DEPENDS=	dbus:primary:std

USES=			meson pkgconfig
GNOME_COMPONENTS=	glib

DISTNAME=		dbus-python-1.4.0

[PY312].BUILD_DEPENDS_ON=		python-wheel:single:v12
					python-setuptools:single:v12
[PY312].MAKE_ENV_ON=			AUTOPYTHON=3.12

[PY313].BUILD_DEPENDS_ON=		python-wheel:single:v13
					python-setuptools:single:v13
[PY313].MAKE_ENV_ON=			AUTOPYTHON=3.13

do-build:
	(cd ${BUILD_WRKSRC} && meson compile)

do-install:
	(cd ${BUILD_WRKSRC} && meson install --destdir "${STAGEDIR}")

[FILE:1335:descriptions/desc.primary]
=======================================
dbus-python_: Python bindings for D-Bus
=======================================

.. _dbus-python:
http://www.freedesktop.org/wiki/Software/DBusBindings#python

dbus-python is the original Python binding for dbus, the reference
implementation of the D-Bus protocol.

Online documentation can be found at
<http://dbus.freedesktop.org/doc/dbus-python/>.

Problems and alternatives
=========================

dbus-python might not be the best D-Bus binding for you to use. dbus-python
does not follow the principle of "In the face of ambiguity, refuse the
temptation to guess", and can't be changed to not do so without seriously
breaking compatibility.

In addition, it uses libdbus (which has known problems with multi-threaded
use) and attempts to be main-loop-agnostic (which means you have to select
a suitable main loop for your application).

Alternative ways to get your Python code onto D-Bus include:

* GDBus, part of the GIO module of `GLib`_, via GObject-Introspection and
  `PyGI`_ (uses the GLib main loop and object model)

* QtDBus, part of `Qt`_, via `PyQt`_ (uses the Qt main loop and object
model)

.. _GLib: http://developer.gnome.org/glib/
.. _PyGI: https://live.gnome.org/PyGObject
.. _Qt:   https://www.qt.io
.. _PyQT: http://www.riverbankcomputing.co.uk/software/pyqt/intro


[FILE:114:distinfo]
991666e498f60dbf3e49b8b7678f5559b8a65034fdf61aae62cdecdb7d89c770       232490 python-src/dbus-python-1.4.0.tar.gz


[FILE:65:manifests/plist.dev]
include/dbus-1.0/dbus/dbus-python.h
lib/pkgconfig/dbus-python.pc


[FILE:238:files/special.mk]
setuptools-autolist:
	# Tailored autolist (avoids catching pc file, supports primary subpackage)
	@(cd ${STAGEDIR}${PREFIX} && \
	${FIND} lib/python* \( -type f -o -type l \) 2>/dev/null | ${SORT}) \
	>> ${WRKDIR}/.manifest.primary.mktmp