openbsd-ports/x11/xscreensaver/patches/patch-driver_Makefile_in

$OpenBSD: patch-driver_Makefile_in,v 1.5 2008/12/28 15:45:31 ajacoutot Exp $
--- driver/Makefile.in.orig	Mon Aug 11 07:11:59 2008
+++ driver/Makefile.in	Thu Oct 23 15:51:54 2008
@@ -10,7 +10,7 @@ VPATH		= @srcdir@
 top_srcdir	= @top_srcdir@
 top_builddir	= ..
 
-install_prefix	=
+install_prefix	= $(DESTDIR)
 prefix		= @prefix@
 exec_prefix	= @exec_prefix@
 bindir		= @bindir@
- remove the unfinished bsd_auth support for now ; I got late on this and I'd rather finish/modify it outside of the tree when I have more time. ok jasper@ 2008-12-28 10:45:31 -05:00			$OpenBSD: patch-driver_Makefile_in,v 1.5 2008/12/28 15:45:31 ajacoutot Exp $
- implement bsd_auth(3) authentication ; benefits: * no need to run xscreensaver setuid root anymore * you can use whatever passwd backend you configured in login.conf(5) (kerberos, ldap...) to unlock the screen and not just local passwd Sent upstream. feedback from millert@ "get it in" jasper@ 2008-10-27 15:49:39 -04:00			`--- driver/Makefile.in.orig Mon Aug 11 07:11:59 2008`
			`+++ driver/Makefile.in Thu Oct 23 15:51:54 2008`
update x11/xscreensaver to 4.05 2002-06-25 22:36:03 -04:00			`@@ -10,7 +10,7 @@ VPATH = @srcdir@`
			`top_srcdir = @top_srcdir@`
			`top_builddir = ..`
The xscreensaver program waits until the keyboard and mouse have been idle for a period, and then runs a graphics demo chosen at random. It turns off as soon as there is any mouse or keyboard activity. It can also lock the screen (immediately, after a longer idle period, or on demand.) xscreensaver consists of two parts: xscreensaver itself, the (the ``driver'' or ``daemon''), which detects idleness and does locking; and the many graphics demos that are launched by xscreensaver. Any X program that can draw on the root window can be used with xscreensaver, regardless of how that program is written, or what language it is written in, or what libraries it uses. The xscreensaver daemon takes care of detecting when the user is idle, locking, and checking passwords and all the other book-keeping; all the other programs need to do is draw. The benefit that xscreensaver has over the combination of the xlock and xautolock programs is the ease with which new graphics hacks can be installed. You don't need to recompile (or even re-run) the xscreensaver program to add a new display mode, you just change a config file. WWW: http://www.jwz.org/xscreensaver/ 2001-06-20 15:16:45 -04:00
			`-install_prefix =`
update xscreensaver to 4.00. 2002-01-26 18:59:49 -05:00			`+install_prefix = $(DESTDIR)`
The xscreensaver program waits until the keyboard and mouse have been idle for a period, and then runs a graphics demo chosen at random. It turns off as soon as there is any mouse or keyboard activity. It can also lock the screen (immediately, after a longer idle period, or on demand.) xscreensaver consists of two parts: xscreensaver itself, the (the ``driver'' or ``daemon''), which detects idleness and does locking; and the many graphics demos that are launched by xscreensaver. Any X program that can draw on the root window can be used with xscreensaver, regardless of how that program is written, or what language it is written in, or what libraries it uses. The xscreensaver daemon takes care of detecting when the user is idle, locking, and checking passwords and all the other book-keeping; all the other programs need to do is draw. The benefit that xscreensaver has over the combination of the xlock and xautolock programs is the ease with which new graphics hacks can be installed. You don't need to recompile (or even re-run) the xscreensaver program to add a new display mode, you just change a config file. WWW: http://www.jwz.org/xscreensaver/ 2001-06-20 15:16:45 -04:00			`prefix = @prefix@`
			`exec_prefix = @exec_prefix@`
			`bindir = @bindir@`