Import bustle-0.2.3.
Bustle draws sequence diagrams of D-Bus activity, showing signal emissions, method calls and their corresponding returns, with timestamps for each individual event and the duration of each method call. This can help you check for unwanted D-Bus traffic, and pinpoint why your D-Bus-based application isn't performing as well as you like. <...> ok kili@ jasper@
This commit is contained in:
parent
95d10b61c2
commit
79bdf9059d
49
devel/bustle/Makefile
Normal file
49
devel/bustle/Makefile
Normal file
@ -0,0 +1,49 @@
|
||||
# $OpenBSD: Makefile,v 1.1.1.1 2010/12/16 19:12:54 ajacoutot Exp $
|
||||
|
||||
COMMENT= D-Bus profiler
|
||||
|
||||
DISTNAME= bustle-0.2.3
|
||||
CATEGORIES= devel
|
||||
|
||||
HOMEPAGE= http://willthompson.co.uk/bustle/
|
||||
|
||||
# LGPLv2.1
|
||||
PERMIT_PACKAGE_CDROM= Yes
|
||||
PERMIT_PACKAGE_FTP= Yes
|
||||
PERMIT_DISTFILES_CDROM= Yes
|
||||
PERMIT_DISTFILES_FTP= Yes
|
||||
|
||||
WANTLIB += GL X11 Xau Xcomposite Xcursor Xdamage Xdmcp Xext Xfixes
|
||||
WANTLIB += Xi Xinerama Xrandr Xrender Xxf86vm atk-1.0 c cairo
|
||||
WANTLIB += dbus-1 drm expat fontconfig freetype gdk-x11-2.0 gdk_pixbuf-2.0
|
||||
WANTLIB += gio-2.0 glade-2.0 glib-2.0 gmodule-2.0 gmp gobject-2.0
|
||||
WANTLIB += gthread-2.0 gtk-x11-2.0 m pango-1.0 pangocairo-1.0
|
||||
WANTLIB += pangoft2-1.0 pixman-1 png pthread pthread-stubs util
|
||||
WANTLIB += xcb xcb-render xcb-shm xml2 z
|
||||
|
||||
MASTER_SITES= ${HOMEPAGE}/releases/
|
||||
|
||||
MODULES= lang/ghc \
|
||||
devel/gettext
|
||||
|
||||
MODGHC_BUILD= cabal nort
|
||||
|
||||
BUILD_DEPENDS= devel/hs-glade \
|
||||
devel/hs-parsec
|
||||
|
||||
LIB_DEPENDS= devel/libglade2 \
|
||||
x11/dbus \
|
||||
devel/gmp
|
||||
|
||||
# no need to install LICENSE in both share{,doc}/${FULLPKGNAME}/
|
||||
pre-configure:
|
||||
perl -pi -e 's,^License-file.*,,' ${WRKSRC}/bustle.cabal
|
||||
|
||||
post-build:
|
||||
perl -pi -e 's,-g -O2,,' ${WRKSRC}/Makefile
|
||||
cd ${WRKBUILD} && ${MAKE_PROGRAM}
|
||||
|
||||
post-install:
|
||||
${INSTALL_PROGRAM} ${WRKBUILD}/bustle-dbus-monitor ${PREFIX}/bin
|
||||
|
||||
.include <bsd.port.mk>
|
5
devel/bustle/distinfo
Normal file
5
devel/bustle/distinfo
Normal file
@ -0,0 +1,5 @@
|
||||
MD5 (bustle-0.2.3.tar.gz) = qXZSflMAQzwxqqB8zX8Crg==
|
||||
RMD160 (bustle-0.2.3.tar.gz) = 2rAxxZ8zpKEbqGdl1efwGpMg8cs=
|
||||
SHA1 (bustle-0.2.3.tar.gz) = goliLkJo0eYANpF1B81pBYucm6I=
|
||||
SHA256 (bustle-0.2.3.tar.gz) = Ki0GM9agcUyEVxX2qkOSsI0dJBGH8isnEiuxv8v20jo=
|
||||
SIZE (bustle-0.2.3.tar.gz) = 39314
|
8
devel/bustle/pkg/DESCR
Normal file
8
devel/bustle/pkg/DESCR
Normal file
@ -0,0 +1,8 @@
|
||||
Bustle draws sequence diagrams of D-Bus activity, showing signal
|
||||
emissions, method calls and their corresponding returns, with timestamps
|
||||
for each individual event and the duration of each method call. This can
|
||||
help you check for unwanted D-Bus traffic, and pinpoint why your
|
||||
D-Bus-based application isn't performing as well as you like.
|
||||
|
||||
There are also command-line tools for generating statistics from D-Bus
|
||||
traces.
|
10
devel/bustle/pkg/PLIST
Normal file
10
devel/bustle/pkg/PLIST
Normal file
@ -0,0 +1,10 @@
|
||||
@comment $OpenBSD: PLIST,v 1.1.1.1 2010/12/16 19:12:54 ajacoutot Exp $
|
||||
@bin bin/bustle
|
||||
@bin bin/bustle-count
|
||||
@bin bin/bustle-dbus-monitor
|
||||
@bin bin/bustle-dot
|
||||
@bin bin/bustle-time
|
||||
share/${FULLPKGNAME}/
|
||||
share/${FULLPKGNAME}/LICENSE
|
||||
share/${FULLPKGNAME}/bustle.glade
|
||||
share/${FULLPKGNAME}/bustle.png
|
Loading…
Reference in New Issue
Block a user