kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/x11/xlockmore/Makefile

115 lines
2.7 KiB
Makefile
Raw Normal View History

Import of xlockmore 1.14
1994-11-09 23:39:07 +01:00
# New ports collection makefile for: xlockmore
Some more ports Makefile updates...sorry, don't have time now so x11/ is only halfway finished.
1995-04-12 17:22:43 +02:00
# Date created: 9 November 1994
# Whom: smace
Import of xlockmore 1.14
1994-11-09 23:39:07 +01:00
#
$Id$ -> $FreeBSD$
1999-08-31 04:51:23 +02:00
# $FreeBSD$
Import of xlockmore 1.14
1994-11-09 23:39:07 +01:00
#
Update to use PORTNAME/PORTVERSION
2000-04-13 21:19:05 +02:00
PORTNAME= xlockmore
- Update to 5.22 PR: ports/96348 Submitted by: UMENO Takashi <umeno@rr.iij4u.or.jp>
2006-04-29 14:13:56 +02:00
PORTVERSION= 5.22
Make some variables ?= because they might be set by slave ports (for example, japanese/xlockmore) PR: ports/59664 (related)
2003-12-29 06:54:34 +01:00
CATEGORIES?= x11
Add MASTER_SITES for more redundancy.
2004-07-27 17:01:19 +02:00
MASTER_SITES= ftp://ftp.tux.org/pub/tux/bagleyd/xlockmore/ \
http://www.tux.org/~bagleyd/latest/
Import of xlockmore 1.14
1994-11-09 23:39:07 +01:00
Make some variables ?= because they might be set by slave ports (for example, japanese/xlockmore) PR: ports/59664 (related)
2003-12-29 06:54:34 +01:00
MAINTAINER?= ports@FreeBSD.org
Clear moonlight beckons. Requiem mors pacem pkg-comment, And be calm ports tree. E Nomini Patri, E Fili, E Spiritu Sancti.
2003-03-07 07:36:20 +01:00
COMMENT= Like XLock session locker/screen saver, but just more
Upgrade to version 3.11.
1996-11-05 08:13:54 +01:00
Upgrade to 5.02.
2001-10-25 13:29:46 +02:00
USE_BZIP2= yes
Upgrade to 4.04.
1997-09-22 09:14:10 +02:00
GNU_CONFIGURE= yes
Tidy up whitespace.
2004-04-10 19:26:55 +02:00
CONFIGURE_ARGS= --without-gl --without-motif --without-sx \
Upgrade to 4.04.
1997-09-22 09:14:10 +02:00
--without-editres --without-dtsaver --without-rplay \
Update to 5.14.1 PR: ports/74466 Submitted by: UMENO Takashi
2004-11-30 17:20:53 +01:00
--without-nas --without-gtk --without-esound \
--without-gtk2
Enable kerberosIV if MAKE_KERBEROS4 is set. Xlock will then get a TGT for the user when she returns and unlocks.
1998-03-20 15:50:09 +01:00
.if defined(MAKE_KERBEROS4)
Tidy up whitespace.
2004-04-10 19:26:55 +02:00
CONFIGURE_ARGS+=--enable-kerberos4
Update to 5.11 [1] Fix build if MAKE_KERBEROS4 defined [2] Make cosmetic changes for pkg-descr, add WWW tag [3] Spotted by: Chris <chris-gnats34@randomcamel.net> [2] Submitted by: UMENO Takashi <umeno@rr.iij4u.or.jp> [1], Volker Stolz <stolz@i2.informatik.rwth-aachen.de> [2], osa [3] PRs: 59882, 60925
2004-01-05 16:43:24 +01:00
KRB4LIB= -lcom_err -lcrypto
Enable kerberosIV if MAKE_KERBEROS4 is set. Xlock will then get a TGT for the user when she returns and unlocks.
1998-03-20 15:50:09 +01:00
.endif
Support Kerberos 5. PR: 18660 Submitted by: wollman
2000-05-19 10:58:41 +02:00
.if defined(KRB5_HOME) && exists(${KRB5_HOME})
Tidy up whitespace.
2004-04-10 19:26:55 +02:00
CONFIGURE_ARGS+=--enable-kerberos5
Add ${KRB5_HOME}/include to $CFLAGS and ${KRB5_HOME}/lib to $XLOCKLIBS for people using kerberos5. Suggested by: Niels Kroon <niels@fundum.net>
2001-09-27 13:44:51 +02:00
CFLAGS+= -I${KRB5_HOME}/include
KRB5LIB= -L${KRB5_HOME}/lib
Support Kerberos 5. PR: 18660 Submitted by: wollman
2000-05-19 10:58:41 +02:00
.endif
Rename all USE_X11 to USE_X_PREFIX. Requires 1.279 (3.0-current) or 1.227.2.41 (2.2-stable) of bsd.port.mk for this to be interpreted correctly.
1998-08-05 11:31:52 +02:00
USE_X_PREFIX= yes
(1) Add new variable, XFREE86_VERSION, to specify which version of XFree86 (3 or 4) to depend to when USE_XLIB is set. XFREE86_VERSION defaults to 3 for now, but adventurous users can override it in /etc/make.conf. When XFREE86_VERSION=3, USE_XLIB will add a dependency to x11/XFree86; when it is set to 4, the dependency will be to x11/XFree86-4-libraries. When XFREE86_VERSION=4, the PKG_IGNORE_DEPENDS and ALWAYS_BUILD_DEPENDS hacks to avoid messing with XFree86 are turned off. Since XFree86 version 4 includes some software that used to be separate ports, when XFREE86_VERSION=3 the following variables are provided: USE_DGS LIB_DEPENDS on x11/dgs USE_FREETYPE LIB_DEPENDS on print/freetype USE_MESA LIB_DEPENDS on graphics/Mesa3 USE_XPM LIB_DEPENDS on graphics/xpm When XFREE86_VERSION=4, these variables have no effect. The LIB_DEPENDS in the tree for the above four ports have all been converted to the USE_* counterparts. For your information, this is the count of the number of ports: USE_DGS 0 USE_FREETYPE 16 USE_MESA 36 USE_XPM 236 There is a new variable, XAWVER, which is set to 6 when XFREE86_VERSION=3 and 7 when XFREE86_VERSION=4. This is also passed to PLIST_SUB so ports that build Xaw based shared libraries can use this variable to substitute the shlib version number. There is also a provision of using a separate mtree file for XFREE86_VERSION=4, but that part is not enabled yet. Reviewed by: the ports list Tested by: make index (XFREE86_VERSION=3 only) (2) Add hebrew to list of valid categories. Submitted by: nbm
2000-08-03 11:28:57 +02:00
USE_XPM= yes
Upgrade to 4.04.
1997-09-22 09:14:10 +02:00
MAN1= xlock.1
xlockmore port improvements patch Some time ago I send PR about PAM support in xlockmore. Now I spend some time to work on xlockmore. I found that PAM works fine by default (with --enable-pam), but only with modules that does not requires root rights to authenticate. But almost all PAM configurations ends with pam_unix call. Here is the trouble. xlock drops root privileges after startup. I use BAD_PAM again to wrap this setuid(). IMHO, usage of BAD_PAM is right in this case. Also abort trap was fixed. Here was error in PAM_conv function. I'll send explanations of changes and situation to xlock-discuss mailing list later. May be fixes will be committed into next release of xlockmore. Here is attached diff against xlockmore port. It makes some changes in Makefile and drops two patches to files dir. New knobs added to Makefile and some old changed. Here is the description: - OPTIONS added for interactive configuration of xlockmore (make config). - WITH_PAM - enable common PAM support in xlock, but does not define BAD_PAM. So PAM modules that does not require root rights can be used (pam_pwdfile e.g.). - WITH_BAD_PAM - enable WITH_PAM and define BAD_PAM in config.h after 'configure'. So all PAM modules can be used, including pam_unix. - WITH_NICE_ONLY - enable only low-CPU modes. Good for old machines. - WITH_BLANK_ONLY - enable only 'blank' mode. Can be useful in some cases. PR: ports/90276 Submitted by: Yuri Y. Bushmelev <jay-dev@simcom.ru>
2005-12-12 22:18:26 +01:00
OPTIONS=MESAGL "Enable Mesa 3D (for GL modes)" off \
MB "Enable Xmb function series" off \
SYSLOG "Enable syslog logging" off \
DISABLE_ALLOW_ROOT "Allows users to turn off allowroot" off \
NICE_ONLY "Enable only low cpu modes" off \
BLANK_ONLY "Enable blank mode only (boring)" off \
PAM "Enable PAM authentication support" off \
BAD_PAM "Xlock will ask PAM with root rights" off
- Update to 5.20.1 PR: ports/88328 Submitted by: Andrew Pantyukhin <infofarmer@gmail.com>
2005-11-01 20:06:10 +01:00
.include <bsd.port.pre.mk>
.if ${ARCH} == amd64
Fix build on AMD64 by disabling MESAGL.
2004-02-10 19:04:08 +01:00
WITH_MESAGL= no
.else
Now that Mesa-3.0 is in with a security fix, bring back the GL modes.
1998-10-01 08:19:19 +02:00
WITH_MESAGL?= yes
Fix build on AMD64 by disabling MESAGL.
2004-02-10 19:04:08 +01:00
.endif
Update to 4.10.
1998-05-20 09:31:01 +02:00
.if ${WITH_MESAGL} == yes
The `--with{,out}-mesagl' option to configure is spelled `--with{,out}-mesa'. PR: 31141 Submitted by: Markus Holmberg <markush+freebsd@acc.umu.se>
2001-10-09 13:24:56 +02:00
CONFIGURE_ARGS+= --with-mesa
. Update to 5.10. [1] . Add some knobs (WITH_MB, XLOCKMORE_LANG). [1] . USE_MESA -> USE_GL. PR: 59139 [1] Submitted by: UMENO Takashi <umeno@rr.iij4u.or.jp> [1]
2003-11-22 00:49:58 +01:00
MESALIB=${PTHREAD_LIBS}
USE_GL= yes
Upgrade to 4.08. Use MesaGL when available.
1998-03-03 09:29:05 +01:00
.else
The `--with{,out}-mesagl' option to configure is spelled `--with{,out}-mesa'. PR: 31141 Submitted by: Markus Holmberg <markush+freebsd@acc.umu.se>
2001-10-09 13:24:56 +02:00
CONFIGURE_ARGS+= --without-mesa --without-opengl
Upgrade to 4.08. Use MesaGL when available.
1998-03-03 09:29:05 +01:00
.endif
. Update to 5.10. [1] . Add some knobs (WITH_MB, XLOCKMORE_LANG). [1] . USE_MESA -> USE_GL. PR: 59139 [1] Submitted by: UMENO Takashi <umeno@rr.iij4u.or.jp> [1]
2003-11-22 00:49:58 +01:00
- Add WITH_NICE_ONLY knob to enable only low-cpu modes. PR: ports/76358 Submitted by: Yuri Y. Bushmelev <jay-dev@simcom.ru>
2005-11-29 19:24:50 +01:00
.if defined(WITH_NICE_ONLY)
CONFIGURE_ARGS+= --enable-nice-only
.endif
- BAD_PAM option now selectable using configure, rather than directly editing config.h. PR: 91907 Submitted by: Tobias Roth <ports@fsck.ch>
2006-01-17 21:51:23 +01:00
.if defined(WITH_BAD_PAM)
CONFIGURE_ARGS+= --enable-bad-pam
xlockmore port improvements patch Some time ago I send PR about PAM support in xlockmore. Now I spend some time to work on xlockmore. I found that PAM works fine by default (with --enable-pam), but only with modules that does not requires root rights to authenticate. But almost all PAM configurations ends with pam_unix call. Here is the trouble. xlock drops root privileges after startup. I use BAD_PAM again to wrap this setuid(). IMHO, usage of BAD_PAM is right in this case. Also abort trap was fixed. Here was error in PAM_conv function. I'll send explanations of changes and situation to xlock-discuss mailing list later. May be fixes will be committed into next release of xlockmore. Here is attached diff against xlockmore port. It makes some changes in Makefile and drops two patches to files dir. New knobs added to Makefile and some old changed. Here is the description: - OPTIONS added for interactive configuration of xlockmore (make config). - WITH_PAM - enable common PAM support in xlock, but does not define BAD_PAM. So PAM modules that does not require root rights can be used (pam_pwdfile e.g.). - WITH_BAD_PAM - enable WITH_PAM and define BAD_PAM in config.h after 'configure'. So all PAM modules can be used, including pam_unix. - WITH_NICE_ONLY - enable only low-CPU modes. Good for old machines. - WITH_BLANK_ONLY - enable only 'blank' mode. Can be useful in some cases. PR: ports/90276 Submitted by: Yuri Y. Bushmelev <jay-dev@simcom.ru>
2005-12-12 22:18:26 +01:00
.endif
- Add WITH_PAM knob. PR: ports/89060 Submitted by: Ronald Klop <ronald@cs.vu.nl>
2005-11-15 12:59:18 +01:00
.if defined(WITH_PAM)
CONFIGURE_ARGS+= --enable-pam
.endif
xlockmore port improvements patch Some time ago I send PR about PAM support in xlockmore. Now I spend some time to work on xlockmore. I found that PAM works fine by default (with --enable-pam), but only with modules that does not requires root rights to authenticate. But almost all PAM configurations ends with pam_unix call. Here is the trouble. xlock drops root privileges after startup. I use BAD_PAM again to wrap this setuid(). IMHO, usage of BAD_PAM is right in this case. Also abort trap was fixed. Here was error in PAM_conv function. I'll send explanations of changes and situation to xlock-discuss mailing list later. May be fixes will be committed into next release of xlockmore. Here is attached diff against xlockmore port. It makes some changes in Makefile and drops two patches to files dir. New knobs added to Makefile and some old changed. Here is the description: - OPTIONS added for interactive configuration of xlockmore (make config). - WITH_PAM - enable common PAM support in xlock, but does not define BAD_PAM. So PAM modules that does not require root rights can be used (pam_pwdfile e.g.). - WITH_BAD_PAM - enable WITH_PAM and define BAD_PAM in config.h after 'configure'. So all PAM modules can be used, including pam_unix. - WITH_NICE_ONLY - enable only low-CPU modes. Good for old machines. - WITH_BLANK_ONLY - enable only 'blank' mode. Can be useful in some cases. PR: ports/90276 Submitted by: Yuri Y. Bushmelev <jay-dev@simcom.ru>
2005-12-12 22:18:26 +01:00
.if defined(WITH_NICE_ONLY)
CONFIGURE_ARGS+= --enable-nice-only
.endif
.if defined(WITH_BLANK_ONLY)
CONFIGURE_ARGS+= --enable-blank-only
.endif
. Update to 5.10. [1] . Add some knobs (WITH_MB, XLOCKMORE_LANG). [1] . USE_MESA -> USE_GL. PR: 59139 [1] Submitted by: UMENO Takashi <umeno@rr.iij4u.or.jp> [1]
2003-11-22 00:49:58 +01:00
.if defined(WITH_MB)
xlockmore port improvements patch Some time ago I send PR about PAM support in xlockmore. Now I spend some time to work on xlockmore. I found that PAM works fine by default (with --enable-pam), but only with modules that does not requires root rights to authenticate. But almost all PAM configurations ends with pam_unix call. Here is the trouble. xlock drops root privileges after startup. I use BAD_PAM again to wrap this setuid(). IMHO, usage of BAD_PAM is right in this case. Also abort trap was fixed. Here was error in PAM_conv function. I'll send explanations of changes and situation to xlock-discuss mailing list later. May be fixes will be committed into next release of xlockmore. Here is attached diff against xlockmore port. It makes some changes in Makefile and drops two patches to files dir. New knobs added to Makefile and some old changed. Here is the description: - OPTIONS added for interactive configuration of xlockmore (make config). - WITH_PAM - enable common PAM support in xlock, but does not define BAD_PAM. So PAM modules that does not require root rights can be used (pam_pwdfile e.g.). - WITH_BAD_PAM - enable WITH_PAM and define BAD_PAM in config.h after 'configure'. So all PAM modules can be used, including pam_unix. - WITH_NICE_ONLY - enable only low-CPU modes. Good for old machines. - WITH_BLANK_ONLY - enable only 'blank' mode. Can be useful in some cases. PR: ports/90276 Submitted by: Yuri Y. Bushmelev <jay-dev@simcom.ru>
2005-12-12 22:18:26 +01:00
CONFIGURE_ARGS+= --enable-use-mb
. Update to 5.10. [1] . Add some knobs (WITH_MB, XLOCKMORE_LANG). [1] . USE_MESA -> USE_GL. PR: 59139 [1] Submitted by: UMENO Takashi <umeno@rr.iij4u.or.jp> [1]
2003-11-22 00:49:58 +01:00
.endif
.if defined(XLOCKMORE_LANG)
Tidy up whitespace.
2004-04-10 19:26:55 +02:00
CONFIGURE_ARGS+= --with-lang=${XLOCKMORE_LANG}
. Update to 5.10. [1] . Add some knobs (WITH_MB, XLOCKMORE_LANG). [1] . USE_MESA -> USE_GL. PR: 59139 [1] Submitted by: UMENO Takashi <umeno@rr.iij4u.or.jp> [1]
2003-11-22 00:49:58 +01:00
.endif
Add WITH_SYSLOG knob. Submitted by: Katsura Matsumoto <katsura@cc.osaka-kyoiku.ac.jp> PR: 62629
2004-02-11 18:47:34 +01:00
.if defined(WITH_SYSLOG)
Tidy up whitespace.
2004-04-10 19:26:55 +02:00
CONFIGURE_ARGS+= --enable-syslog
Add WITH_SYSLOG knob. Submitted by: Katsura Matsumoto <katsura@cc.osaka-kyoiku.ac.jp> PR: 62629
2004-02-11 18:47:34 +01:00
.endif
Fix building when MAKE_KERBEROS4 is defined.
2002-04-02 13:49:49 +02:00
CONFIGURE_ENV+= XLOCKLIBS="${KRB5LIB} ${KRB4LIB} ${MESALIB}"
Upgrade to 4.08. Use MesaGL when available.
1998-03-03 09:29:05 +01:00
Add a knob to disable the `allow-root' functionality, which lets root unlock the screensaver regardless of the current owner. Submitted by: Anders Nordby <anders@fix.no>
2001-07-12 13:41:06 +02:00
.if defined(WITH_DISABLE_ALLOW_ROOT)
CONFIGURE_ARGS+= --disable-allow-root
.endif
xlockmore port improvements patch Some time ago I send PR about PAM support in xlockmore. Now I spend some time to work on xlockmore. I found that PAM works fine by default (with --enable-pam), but only with modules that does not requires root rights to authenticate. But almost all PAM configurations ends with pam_unix call. Here is the trouble. xlock drops root privileges after startup. I use BAD_PAM again to wrap this setuid(). IMHO, usage of BAD_PAM is right in this case. Also abort trap was fixed. Here was error in PAM_conv function. I'll send explanations of changes and situation to xlock-discuss mailing list later. May be fixes will be committed into next release of xlockmore. Here is attached diff against xlockmore port. It makes some changes in Makefile and drops two patches to files dir. New knobs added to Makefile and some old changed. Here is the description: - OPTIONS added for interactive configuration of xlockmore (make config). - WITH_PAM - enable common PAM support in xlock, but does not define BAD_PAM. So PAM modules that does not require root rights can be used (pam_pwdfile e.g.). - WITH_BAD_PAM - enable WITH_PAM and define BAD_PAM in config.h after 'configure'. So all PAM modules can be used, including pam_unix. - WITH_NICE_ONLY - enable only low-CPU modes. Good for old machines. - WITH_BLANK_ONLY - enable only 'blank' mode. Can be useful in some cases. PR: ports/90276 Submitted by: Yuri Y. Bushmelev <jay-dev@simcom.ru>
2005-12-12 22:18:26 +01:00
.if defined(WITH_PAM) && !defined (WITH_BAD_PAM)
pre-extract:
@${ECHO}
@${ECHO} "You have enabled PAM support. If you want to authenticate against"
@${ECHO} "root only accessible PAM modules then define WITH_BAD_PAM=yes also."
@${ECHO} "For example, pam_unix requires root rights to access shadow passwords."
@${ECHO}
.endif
Upgrade to 4.17. XFree86-4 users: please test this port. According to the docs, xlock should compile now. (I can't try it, I'm still running XFree86-3.3.6.)
2000-08-15 16:07:24 +02:00
post-configure:
xlockmore port improvements patch Some time ago I send PR about PAM support in xlockmore. Now I spend some time to work on xlockmore. I found that PAM works fine by default (with --enable-pam), but only with modules that does not requires root rights to authenticate. But almost all PAM configurations ends with pam_unix call. Here is the trouble. xlock drops root privileges after startup. I use BAD_PAM again to wrap this setuid(). IMHO, usage of BAD_PAM is right in this case. Also abort trap was fixed. Here was error in PAM_conv function. I'll send explanations of changes and situation to xlock-discuss mailing list later. May be fixes will be committed into next release of xlockmore. Here is attached diff against xlockmore port. It makes some changes in Makefile and drops two patches to files dir. New knobs added to Makefile and some old changed. Here is the description: - OPTIONS added for interactive configuration of xlockmore (make config). - WITH_PAM - enable common PAM support in xlock, but does not define BAD_PAM. So PAM modules that does not require root rights can be used (pam_pwdfile e.g.). - WITH_BAD_PAM - enable WITH_PAM and define BAD_PAM in config.h after 'configure'. So all PAM modules can be used, including pam_unix. - WITH_NICE_ONLY - enable only low-CPU modes. Good for old machines. - WITH_BLANK_ONLY - enable only 'blank' mode. Can be useful in some cases. PR: ports/90276 Submitted by: Yuri Y. Bushmelev <jay-dev@simcom.ru>
2005-12-12 22:18:26 +01:00
.if ${X_WINDOW_SYSTEM:L} != xfree86-3
Use REINPLACE_CMD. PR: 50843 Submitted by: Ulrich Spoerlein <q@uni.de>
2003-05-09 17:42:24 +02:00
${REINPLACE_CMD} -e 's/-lXdpms//g' ${WRKSRC}/modes/Makefile
Upgrade to 4.17. XFree86-4 users: please test this port. According to the docs, xlock should compile now. (I can't try it, I'm still running XFree86-3.3.6.)
2000-08-15 16:07:24 +02:00
.endif
- Update to 5.16 - Use PLIST_FILES (me) PR: ports/79516 Submitted by: UMENO Takashi
2005-04-04 16:45:55 +02:00
PLIST_FILES= bin/xlock lib/X11/app-defaults/XLock
Use bsd.port.{pre,post}.mk. Either use them to avoid having to define something already there (PORTOBJFORMAT, OSVERSION) or move stuff from after .include <bsd.port.mk> to before. (This is not by any means the complete list but just the ones I've noticed recently.)
1998-11-11 06:37:39 +01:00
.include <bsd.port.post.mk>
Reference in a new issue Copy permalink