summaryrefslogtreecommitdiff
path: root/mk
AgeCommit message (Collapse)AuthorFilesLines
2001-11-30Move code from end of the do-configure target that performed thejlam1-9/+24
LIBTOOL_OVERRIDE steps into a separate do-libtool-override target. Create a new variable _CONFIGURE_POSTREQ that currently lists do-libtool-override. Also add some documentation for the two _CONFIGURE_* variables: _CONFIGURE_PREREQ is a list of targets to run after pre-configure but before do-configure. These targets typically edit the files used by the do-configure target. _CONFIGURE_POSTREQ is a list of targets to run after do-configure but before post-configure. These targets typically edit the files generated by the do-configure target that are used during the build phase.
2001-11-30Move the REPLACE_PERL code into a separate configure pre-requisite targetjlam1-9/+15
"replace-perl", instead of keeping it as part of the do-patch target. Now, a "make patch" will result in just the patched sources.
2001-11-30Rename "do-libtool" target to "do-ltconfig-override" as the new name is morejlam1-3/+3
descriptive. There is a separate step to replace the actual libtool script that is controlled by LIBTOOL_OVERRIDE within the "do-configure" target.
2001-11-30Remove REPLACE_CURSES from bsd.pkg.mk (not needed anymore), and don'twiz1-17/+1
document it and USE_CURSES in Packages.txt anymore (packages should really use devel/ncurses/buildlink.mk instead).
2001-11-30Update XCONTRIB path for .at.wiz1-2/+2
2001-11-29Drop a line of the form '^<TAB>$'.wiz1-2/+1
2001-11-29Get rid of manually adding "nbX" to PKGNAME when a pkg was changed inhubertf1-1/+9
pkgsrc. Instead, a new variable PKGREVISION is invented that can get bumped independent of DISTNAME and PKGNAME. Example #1: DISTNAME= foo-X.Y PKGREVISION= Z => PKGNAME= foo-X.YnbZ Example #2: DISTNAME= barthing-X.Y PKGNAME= bar-X.Y PKGREVISION= Z => PKGNAME= bar=X.YnbZ (!) On subsequent changes, only PKGREVISION needs to be bumped, no more risk of getting DISTNAME changed accidentally.
2001-11-28In the odd possible case of someone using "pkgsrc" underneath "src"tv1-1/+6
(even though that's still a bad idea), set USETOOLS=no explicitly before including <bsd.own.mk>, and add this also to MAKE_ENV to make BSD-Makefile based packages build properly.
2001-11-28Move the PKG_SYSCONFDIR logic below the definition of PKGNAME. PKGNAME isjlam1-31/+31
use to set PKGBASE, which is used in the name of the package-specific config directory override (PKG_SYSCONFDIR.${PKGBASE}). Prior to this, if PKGNAME wasn't explicitly set in the package, then the override would not work.
2001-11-28cvsweb also implicitly used ${APACHE_SYSCONFDIR} as its config filejlam1-1/+2
directory.
2001-11-28Fix problem where bsd.pkg.obsolete.mk wouldn't be found when "make" wasjlam1-2/+8
executed outside of a package directory. Problem and fix noted by Stoned Elipot in private email.
2001-11-28lose some more pkg/ referencesabs3-10/+10
2001-11-27Add commented-out entry for GQMPEG_NO_RUSSIANhubertf1-2/+7
2001-11-26Replace PKG_{USER,GROUP} with PKG_USERS and PKG_GROUPS:jlam4-113/+177
PKG_USERS represents the users to create for the package. It is a space-separated list of elements of the form user:group[:[userid][:[descr][:[home][:shell]]]] Only the user and group are required; everything else is optional, but the colons must be in the right places when specifying optional bits. Note that if the description contains spaces, then spaces should be double backslash-escaped, e.g. foo:foogrp::The\\ Foomister PKG_GROUPS represents the groups to create for the package. It is a space-separated list of elements of the form group[:groupid] Only the group is required; the groupid is optional. This solves the problem of what to do when there is more than one user or group needed for a package, e.g. qmail. Also add a bit more error-checking to the INSTALL/DEINSTALL scripts.
2001-11-26fetch-list: properly quote URLs printed, as they may contain things thathubertf1-2/+2
the shell doesn't like. Fixes PR 14347 by Ben Wong <Benjamin.Wong@cc.gatech.edu>
2001-11-26In fit of paranoia after reading about the iTunes installer and given wejlam2-82/+99
now work on Darwin, and then the discussion about allowing spaces in user/group names, make these scripts work even if the inputs contain spaces. Yes, this is overkill, but after doing all of the work, I didn't want to waste it.
2001-11-26p5-HTTPD-User-Manage also used APACHE_SYSCONFDIR (implicitly). Alsojlam1-11/+12
re-indent for aesthetic considerations.
2001-11-26Run "make bulk-package" with stdin redirected from /dev/null,hubertf1-2/+2
to prevent it sitting there for days waiting for input in useless situations.
2001-11-25fix typo in error output message (s/PKNAME/PKGNAME). Patch fromdmcmahill1-2/+2
Hubert Feyrer.
2001-11-25Fix pasto: PKG_GROUP -> PKG_USERID.jlam1-2/+2
2001-11-25Check for an empty value for PKG_SYSCONFSUBDIR and set PKG_SYSCONFDIRjlam1-1/+5
accordingly so that config files are in /usr/pkg/etc/foo.conf, and not /usr/pkg/etc//foo.conf.
2001-11-25www/apc-gui also used APACHE_SYSCONFDIR.jlam1-1/+2
2001-11-25Deprecate APACHE_SYSCONFDIR, PHP_CONFDIR, VTUN_SYSCONFDIR by moving themjlam1-22/+2
to bsd.pkg.obsolete.mk.
2001-11-25This file holds make(1) logic to allow obsolete or deprecated variablesjlam1-0/+23
still to be used. These may eventually disappear over time as the contents are, by definition, obsolete and deprecated.
2001-11-25Pass PKG_SYSCONFDIR to the configure and build processes.jlam1-1/+4
2001-11-25PKG_SYSCONFDIR is where the configuration files for a package may be found.jlam2-9/+26
This value may be customized in various ways: PKG_SYSCONFBASE is the main config directory under which all package configuration files are to be found. PKG_SYSCONFSUBDIR is the subdirectory of PKG_SYSCONFBASE under which the configuration files for a particular package may be found. PKG_SYSCONFDIR.${PKGBASE} overrides the value of ${PKG_SYSCONFDIR} for a particular package. Users will typically want to set PKG_SYSCONFBASE to /etc, or accept the default location of ${PREFIX}/etc. This obsoletes the use of CONFDIR, which was active for only 6 days, so no need to have a workaround to still accept old CONFDIR settings.
2001-11-25Allow ALL_{DIRS,FILES,MAKE_DIRS} to be appended to by the extra templatesjlam2-5/+9
so that the general INSTALL/DEINSTALL scripts can manage these extra files and directories.
2001-11-23Change SQUID_SYSCONF_DIR to SQUID_SYSCONFDIR to match www/squid/Makefilekim1-2/+2
2001-11-23Add SU to FILES_SUBSTabs1-1/+2
2001-11-23Add documentation of variable "SQUID_SYSCONFDIR".tron1-1/+6
2001-11-22Add a new option "MUTT_USE_SLANG" to use the "slang" library instead oftron1-2/+7
"curses" because the first deals with resize better, especially under NetBSD 1.5/1.5.x. This change was suggested by Joe Abley in PR pkg/13630.
2001-11-21Now that all the files have been moved into the main package directory,agc1-13/+1
remove the temporary ${PKGDIR} workaround.
2001-11-21Refer to /etc/rc.d as ${RCD_SCRIPTS_DIR} more thoroughly.jlam1-3/+3
2001-11-21Change the way the RCD_SCRIPTS variable is used. It now just lists thejlam4-9/+22
names of the scripts and is no longer a MLINKS-type variable. The scripts are copied into ${RCD_SCRIPTS_DIR} which defaults to /etc/rc.d for now. It's unclear if Linux/Solaris would set RCD_SCRIPTS_DIR to something else.
2001-11-21Move some operating-system specific definitions to the individualagc5-106/+89
defs.${OPSYS}.mk files.
2001-11-21Add an _OPSYS_HAS_OSSAUDIO definition to the individual defs.${OPSYS}.mkagc5-6/+10
files, and use it in ossaudio.buildlink.mk. The definition shows whether or not libossaudio is available in the OS.
2001-11-21Move MOTIF_TYPE_DEFAULT and MOTIF12_TYPE_DEFAULT definitions into theagc5-24/+13
individual defs.${OPSYS}.mk files. No change in functionality.
2001-11-21Add _OPSYS_HAS_MANZ and _PREFORMATTED_MAN_DIR definitions to theagc5-40/+48
individual defs.${OPSYS}.mk files, and use them in bsd.pkg.mk. + _OPSYS_HAS_MANZ defines whether or not the OS does MANZ handling as standard + _PREFORMATTED_MAN_DIR is the name of directory (cat or man) where preformatted manual pages go. Rename the internal definitions used in the generation of PLIST files to start with '_'. This completes the "generic" changes to bsd.pkg.mk.
2001-11-21Add a _DO_SHLIB_CHECKS definition to the individual defs.${OPSYS}.mkagc5-7/+11
files, and use it in bsd.pkg.mk. This definition controls the fixup of PLISTs at installation time, and running of ldconfig if necessary.
2001-11-21Add a _PATCH_BACKUP_ARG definition to the individual defs.${OPSYS}.mk files,agc5-10/+10
and use it in bsd.pkg.mk. This definition is the switch to patch(1) to provide backup files when patching.
2001-11-21Add a _USE_RPATH definition to the individual defs.${OPSYS}.mk files,agc5-6/+10
and use it in bsd.pkg.mk. This definition says whether or not the rpath is to be added to the LDFLAGS definition.
2001-11-21Add a _DO_LIBINTL_CHECKS definition to the individual defs,${OPSYS}.mkagc5-6/+10
files, and use it in bsd.pkg.mk. If set to "yes", checks that a valid libintl library and header file should be performed.
2001-11-21Add a definition of _IMAKE_MAKE to the individual defs.${OPSYS}.mkagc5-7/+15
files, defined to be the make program which is invoked by imake, and use it accordingly in bsd.pkg.mk
2001-11-21Move default umask for operating systems into the individual defs.${OPSYS}.mkagc5-17/+13
files, rather than switching by ${OPSYS} within bsd.pkg.mk.
2001-11-21Forgot an EOF in the last commit.jlam1-1/+2
2001-11-20Remind the user that some rc.conf settings may need to be removed afterjlam1-1/+8
the package has been deleted.
2001-11-20We should only depend on sysutils/user in the !exists(/usr/sbin/user) case.jlam1-2/+2
2001-11-20Add definitions for ROOT_USER and ROOT_GROUP that are the symbolic names ofjlam4-4/+16
the root user and root group.
2001-11-19For completeness, add a SUPPORT_FILES_PERMS that acts like CONF_FILES_PERMSjlam4-24/+29
but the user isn't prompted to customize the files at post-install time.
2001-11-19Common INSTALL/DEINSTALL scripts and Makefile magic to automatically performjlam5-0/+577
many of the tasks that need to be done when package is installed or deinstalled: * creating user/group for the package, * creating and removing directories with special permissions and ownership, * copying config files to their final locations, and removing them at deinstall time if they don't differ from the example ones, * reminding the package admin of files he may want to customize or of files/directories he may want to remove.