kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/sysutils/hal/Makefile

125 lines
3.6 KiB
Makefile
Raw Normal View History

Bump all packages that use perl, or depend on a p5-* package, or are called p5-*. I hope that's all of them.
2012-10-03 23:53:53 +02:00
# $NetBSD: Makefile,v 1.63 2012/10/03 21:57:38 wiz Exp $
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
Update to 0.5.14. Many bugfixes and support for new features.
2010-12-26 21:59:31 +01:00
DISTNAME= hal-0.5.14
Bump all packages that use perl, or depend on a p5-* package, or are called p5-*. I hope that's all of them.
2012-10-03 23:53:53 +02:00
PKGREVISION= 9
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
CATEGORIES= sysutils
MASTER_SITES= http://hal.freedesktop.org/releases/
EXTRACT_SUFX= .tar.bz2
to netbsd-desktop
2009-03-18 14:30:45 +01:00
MAINTAINER= netbsd-desktop@NetBSD.org
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
HOMEPAGE= http://hal.freedesktop.org/
COMMENT= FreeDesktop hardware abstraction layer
Added LICENSE information.
2010-01-24 18:11:17 +01:00
LICENSE= gnu-gpl-v2
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
Make the package fully honour PKG_SYSCONFBASE. Bump revision.
2008-12-26 12:36:31 +01:00
BUILD_DEFS+= VARBASE PKG_SYSCONFBASE
DESTDIR ready.
2008-12-03 08:38:10 +01:00
PKG_DESTDIR_SUPPORT= user-destdir
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
GNU_CONFIGURE= YES
USE_PKGLOCALEDIR= YES
USE_TOOLS+= gmake intltool msgfmt perl pkg-config
Initial import of NetBSD HAL backend. It doesn't do much useful yet, but keeping things here makes development easier. Bump PKGREVISION.
2008-11-26 00:10:23 +01:00
USE_TOOLS+= autoconf automake autoreconf
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
USE_LIBTOOL= YES
Use MAKE_DIRS and OWN_DIRS instead of INSTALL as suggested by Joerg.
2009-02-28 15:54:23 +01:00
MAKE_DIRS+= /media
MAKE_DIRS+= ${VARBASE}/cache/hald
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
SPECIAL_PERMS+= ${VARBASE}/cache/hald ${HAL_USER} ${HAL_GROUP} 0644
EGDIR= ${PREFIX}/share/examples/hal
Honour PKG_SYSCONFBASE when installing dbus policy.
2008-12-08 21:26:13 +01:00
CONF_FILES= ${EGDIR}/hal.conf ${PKG_SYSCONFBASE}/dbus-1/system.d/hal.conf
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
Make the package fully honour PKG_SYSCONFBASE. Bump revision.
2008-12-26 12:36:31 +01:00
CONFIGURE_ARGS+= --sysconfdir=${PKG_SYSCONFBASE}
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
CONFIGURE_ARGS+= --localstatedir=${VARBASE}
* Make it work on DragonFly with FreeBSD backend. It's largely untested, but certainly already usable. * Fix paths to [pci|usb].ids files. * Bump PKGREVISION.
2008-11-24 22:13:19 +01:00
CONFIGURE_ARGS+= --with-pci-ids=${PREFIX}/share/pciids
CONFIGURE_ARGS+= --with-usb-ids=${PREFIX}/share/usbids
Readd --without-os-type configure arg, accidentally dropped when merging the 0.5.14 changes. PR#44703
2011-03-10 20:45:03 +01:00
CONFIGURE_ARGS+= --without-os-type
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
* Make it build in DragonFly * Fix PLIST * Bump PKGREVISION
2008-11-23 22:50:51 +01:00
.include "../../mk/bsd.prefs.mk"
Bump PKGREVISION * Fix build on FreeBSD 9.0 ** Patches are borrowed from FreeBSD ports ** Split FreeBSD support from DragonFly/FreeBSD support
2012-03-31 18:06:56 +02:00
.if ${OPSYS} == "DragonFly"
.include "../../devel/libvolume_id/buildlink3.mk"
CONFIGURE_ARGS+= --with-eject=/usr/sbin/cdcontrol
CONFIGURE_ARGS+= --with-backend=freebsd
PLIST_SRC= PLIST.DragonFly PLIST
.elif ${OPSYS} == "FreeBSD"
PR# pkg/40230: "libvolume_id" doesn't build under Mac OS X HAL uses the dummy backend on OSX, so no need to pull in libvolume_id.
2008-12-20 00:13:24 +01:00
.include "../../devel/libvolume_id/buildlink3.mk"
* Make it build in DragonFly * Fix PLIST * Bump PKGREVISION
2008-11-23 22:50:51 +01:00
CONFIGURE_ARGS+= --with-eject=/usr/sbin/cdcontrol
* Make it work on DragonFly with FreeBSD backend. It's largely untested, but certainly already usable. * Fix paths to [pci|usb].ids files. * Bump PKGREVISION.
2008-11-24 22:13:19 +01:00
CONFIGURE_ARGS+= --with-backend=freebsd
Unbreak the build in DragonFly again.
2008-12-16 11:09:32 +01:00
PLIST_SRC= PLIST.FreeBSD PLIST
* Make it build in DragonFly * Fix PLIST * Bump PKGREVISION
2008-11-23 22:50:51 +01:00
Rework platform logic to fall back properly to dummy backend.
2008-12-21 15:17:20 +01:00
.elif !empty(MACHINE_PLATFORM:MNetBSD-[5-9]*)
PR# pkg/40230: "libvolume_id" doesn't build under Mac OS X HAL uses the dummy backend on OSX, so no need to pull in libvolume_id.
2008-12-20 00:13:24 +01:00
.include "../../devel/libvolume_id/buildlink3.mk"
Initial import of NetBSD HAL backend. It doesn't do much useful yet, but keeping things here makes development easier. Bump PKGREVISION.
2008-11-26 00:10:23 +01:00
CONFIGURE_ARGS+= --with-backend=netbsd
hald-netbsd: add basic support for automounting non-optical media. Still some bugs to work out, but it's a start. Bump PKGREVISION.
2008-12-01 03:02:33 +01:00
HAL_GROUP= operator
Initial import of NetBSD HAL backend. It doesn't do much useful yet, but keeping things here makes development easier. Bump PKGREVISION.
2008-11-26 00:10:23 +01:00
Rework platform logic to fall back properly to dummy backend.
2008-12-21 15:17:20 +01:00
.elif ${OPSYS} == "Linux"
Fixes for Linux build: - Pull in libblkid for Linux in order to successfully build - Fix PLIST.Linux: lib/hal -> libexec - Remove Linux-only libusb buildlink. This version of hal fails to use libusb, since it isn't version 2.0 (this does look a little like a mistake though). - The CSR support is absent because libusb isn't available. Remove from PLIST.Linux - Other minor additions and edits to PLIST.Linux - Buildlink in gperf explicitly, to reliably build the keymap support - Make sure .../etc/udev/rules.d exists before trying to install to it
2011-01-09 02:26:56 +01:00
.include "../../devel/gperf/buildlink3.mk"
.include "../../devel/libblkid/buildlink3.mk"
PR# pkg/40230: "libvolume_id" doesn't build under Mac OS X HAL uses the dummy backend on OSX, so no need to pull in libvolume_id.
2008-12-20 00:13:24 +01:00
.include "../../devel/libvolume_id/buildlink3.mk"
Initial import of NetBSD HAL backend. It doesn't do much useful yet, but keeping things here makes development easier. Bump PKGREVISION.
2008-11-26 00:10:23 +01:00
.include "../../sysutils/pciutils/buildlink3.mk"
CONFIGURE_ARGS+= --with-backend=linux
Fixes for Linux build: - Pull in libblkid for Linux in order to successfully build - Fix PLIST.Linux: lib/hal -> libexec - Remove Linux-only libusb buildlink. This version of hal fails to use libusb, since it isn't version 2.0 (this does look a little like a mistake though). - The CSR support is absent because libusb isn't available. Remove from PLIST.Linux - Other minor additions and edits to PLIST.Linux - Buildlink in gperf explicitly, to reliably build the keymap support - Make sure .../etc/udev/rules.d exists before trying to install to it
2011-01-09 02:26:56 +01:00
MAKE_DIRS+= ${PKG_SYSCONFBASE}/udev
MAKE_DIRS+= ${PKG_SYSCONFBASE}/udev/rules.d
PR# pkg/40147: sysutils/hal fails to build on Linux
2008-12-21 14:58:28 +01:00
CONF_FILES+= ${EGDIR}/90-hal.rules \
${PKG_SYSCONFBASE}/udev/rules.d/90-hal.rules
Rework platform logic to fall back properly to dummy backend.
2008-12-21 15:17:20 +01:00
.else # Unsupported systems
# Pull in the dummy backend
Fix build on NetBSD 4
2011-05-07 12:07:12 +02:00
.include "../../devel/libvolume_id/buildlink3.mk"
Rework platform logic to fall back properly to dummy backend.
2008-12-21 15:17:20 +01:00
CONFIGURE_ARGS+= --with-backend=dummy
PLIST_SRC= PLIST
Initial import of NetBSD HAL backend. It doesn't do much useful yet, but keeping things here makes development easier. Bump PKGREVISION.
2008-11-26 00:10:23 +01:00
.endif
Couple of hacks to get Sun Studio compile working.
2009-01-23 12:13:38 +01:00
CFLAGS.SunOS+= -Du_int32_t=uint32_t
Fix build on SunOS.
2011-04-04 11:41:17 +02:00
.if ${OPSYS} == "Darwin" || ${OPSYS} == "SunOS"
PR# pkg/40230: "libvolume_id" doesn't build under Mac OS X Fix HAL build on OS X. Tested on 10.5.6 powerpc.
2008-12-20 22:11:05 +01:00
BUILDLINK_TRANSFORM+= rm:-Wl,--as-needed
.endif
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
REPLACE_INTERPRETER+= bash
REPLACE.bash.old= /bin/bash
REPLACE.bash.new= ${SH}
.for halscript in luks-remove luks-setup luks-teardown system-wol-enable system-wol-enabled system-wol-supported
REPLACE_FILES.bash+= tools/hal-${halscript}
.endfor
hald-netbsd: add basic support for automounting non-optical media. Still some bugs to work out, but it's a start. Bump PKGREVISION.
2008-12-01 03:02:33 +01:00
HAL_USER?= haldaemon
HAL_GROUP?= haldaemon
CONFIGURE_ARGS+= --with-hal-user=${HAL_USER}
CONFIGURE_ARGS+= --with-hal-group=${HAL_GROUP}
PR# pkg/40230: "libvolume_id" doesn't build under Mac OS X Fix HAL build on OS X. Tested on 10.5.6 powerpc.
2008-12-20 22:11:05 +01:00
CONFIGURE_ARGS+= --disable-pmu
hald-netbsd: add basic support for automounting non-optical media. Still some bugs to work out, but it's a start. Bump PKGREVISION.
2008-12-01 03:02:33 +01:00
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
RCD_SCRIPTS= hal
hald-netbsd: add basic support for automounting non-optical media. Still some bugs to work out, but it's a start. Bump PKGREVISION.
2008-12-01 03:02:33 +01:00
.if ${HAL_GROUP} != "operator"
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
PKG_GROUPS= ${HAL_GROUP}
hald-netbsd: add basic support for automounting non-optical media. Still some bugs to work out, but it's a start. Bump PKGREVISION.
2008-12-01 03:02:33 +01:00
.endif
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
PKG_USERS= ${HAL_USER}:${HAL_GROUP}
PKG_HOME.haldaemon= ${VARBASE}/run/hal
FILES_SUBST+= HAL_USER=${HAL_USER}
FILES_SUBST+= HAL_GROUP=${HAL_GROUP}
Actually substitute "PKG_SYSCONFBASE" in the package list. Bump package revisions as this affects the binary package.
2009-03-02 12:36:33 +01:00
PLIST_SUBST+= PKG_SYSCONFDIR=${PKG_SYSCONFDIR}
Added missing TEST_TARGET.
2010-01-16 15:46:36 +01:00
TEST_TARGET= check
Initial import of NetBSD HAL backend. It doesn't do much useful yet, but keeping things here makes development easier. Bump PKGREVISION.
2008-11-26 00:10:23 +01:00
post-extract:
${CP} -r ${FILESDIR}/hald-netbsd ${WRKSRC}/hald/netbsd
Add reboot, shutdown, suspend support. Bump PKGREVISION.
2008-11-27 04:32:19 +01:00
${CP} -r ${FILESDIR}/tools-netbsd ${WRKSRC}/tools/netbsd
Initial import of NetBSD HAL backend. It doesn't do much useful yet, but keeping things here makes development easier. Bump PKGREVISION.
2008-11-26 00:10:23 +01:00
pre-configure:
Use ${AUTORECONF_ARGS} to work with native pkg-config.
2011-09-14 19:44:55 +02:00
cd ${WRKSRC} && autoreconf -vi ${AUTORECONF_ARGS}
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
.include "../../devel/GConf/schemas.mk"
.include "../../devel/glib2/buildlink3.mk"
.include "../../misc/pciids/buildlink3.mk"
.include "../../misc/usbids/buildlink3.mk"
.include "../../security/policykit/buildlink3.mk"
.include "../../sysutils/dbus/buildlink3.mk"
.include "../../sysutils/dbus-glib/buildlink3.mk"
.include "../../sysutils/hal-info/buildlink3.mk"
PR# pkg/40230: "libvolume_id" doesn't build under Mac OS X Fix HAL build on OS X. Tested on 10.5.6 powerpc.
2008-12-20 22:11:05 +01:00
.include "../../textproc/expat/buildlink3.mk"
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink