summaryrefslogtreecommitdiff
path: root/security/PAM
AgeCommit message (Collapse)AuthorFilesLines
2006-04-12Aligned the last line of the buildlink3.mk files with the first line, sorillig1-2/+2
that they look nicer.
2006-04-06Over 1200 files touched but no revisions bumped :)reed2-5/+5
RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-03-30Avoid extra stat() calls by not repeatedly checking whether a filejlam1-2/+2
exists on the disk -- we can just check whether a variable defined by find-files.mk is "__nonexistent__" or not.
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg2-4/+4
2005-12-29Remove USE_PKGINSTALL from pkgsrc now that mk/install/pkginstall.mkjlam1-2/+1
automatically detects whether we want the pkginstall machinery to be used by the package Makefile.
2005-12-05Ran "pkglint --autofix", which corrected some of the quoting issues inrillig1-2/+2
CONFIGURE_ARGS.
2005-12-05Fixed pkglint warnings. The warnings are mostly quoting issues, forrillig1-2/+2
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some other changes are outlined in http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
2005-10-04For --enable-mandir use ${PKGMANDIR}.reed1-2/+2
2005-09-08Define USE_GETLOGIN for preprocessor instead so it later just DTRT.salo1-3/+2
Should fix PR pkg/30965 (the same issue was uncovered while working on a pullup ticket #738)
2005-06-01Massive cleanup of buildlink3.mk and builtin.mk files in pkgsrc.jlam1-29/+52
Several changes are involved since they are all interrelated. These changes affect about 1000 files. The first major change is rewriting bsd.builtin.mk as well as all of the builtin.mk files to follow the new example in bsd.builtin.mk. The loop to include all of the builtin.mk files needed by the package is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk is now included by each of the individual builtin.mk files and provides some common logic for all of the builtin.mk files. Currently, this includes the computation for whether the native or pkgsrc version of the package is preferred. This causes USE_BUILTIN.* to be correctly set when one builtin.mk file includes another. The second major change is teach the builtin.mk files to consider files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most of the builtin.mk files test for the presence of built-in software by checking for the existence of certain files, e.g. <pthread.h>, and we now assume that if that file is under ${LOCALBASE}, then it must be from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The exceptions to this new check are the X11 distribution packages, which are handled specially as noted below. The third major change is providing builtin.mk and version.mk files for each of the X11 distribution packages in pkgsrc. The builtin.mk file can detect whether the native X11 distribution is the same as the one provided by pkgsrc, and the version.mk file computes the version of the X11 distribution package, whether it's built-in or not. The fourth major change is that the buildlink3.mk files for X11 packages that install parts which are part of X11 distribution packages, e.g. Xpm, Xcursor, etc., now use imake to query the X11 distribution for whether the software is already provided by the X11 distribution. This is more accurate than grepping for a symbol name in the imake config files. Using imake required sprinkling various builtin-imake.mk helper files into pkgsrc directories. These files are used as input to imake since imake can't use stdin for that purpose. The fifth major change is in how packages note that they use X11. Instead of setting USE_X11, package Makefiles should now include x11.buildlink3.mk instead. This causes the X11 package buildlink3 and builtin logic to be executed at the correct place for buildlink3.mk and builtin.mk files that previously set USE_X11, and fixes packages that relied on buildlink3.mk files to implicitly note that X11 is needed. Package buildlink3.mk should also include x11.buildlink3.mk when linking against the package libraries requires also linking against the X11 libraries. Where it was obvious, redundant inclusions of x11.buildlink3.mk have been removed.
2005-05-31Packages have no business modifying PKG_DEFAULT_OPTIONS -- it's adillo1-5/+2
user settable variable. Set PKG_SUGGESTED_OPTIONS instead. Also, make use of PKG_OPTIONS_LEGACY_VARS. Reviewed by wiz.
2005-05-22Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:jlam1-2/+2
USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-03-24Don't check for USE_BUILDLINK3 anymore in these files. These are includedjlam1-4/+2
by other package Makefiles, and with the deprecation of USE_BUILDLINK3 support in the infrastructure files, these had the potential to break existing packages.
2005-02-24Add RMD160 digests.agc1-1/+2
2005-01-14Modify linux-pam and solaris-pam builtin.mk files to be more generaljlam1-18/+19
in their tests for built-in versions of the PAM implementations. The MacOS X case now collapses nicely into the linux-pam case. Allow pam.buildlink3.mk to use solaris-pam as an accepted PAM implementation.
2005-01-14Create a pam.buildlink3.mk file that is used by PAM-using packages.jlam1-4/+4
It includes the correct buildlink3.mk file from either Linux-PAM (security/PAM) or OpenPAM (security/openpam) and eventually will support solaris-pam. pam.buildlink3.mk will: * set PAMBASE to the base directory of the PAM files; * set PAM_TYPE to the PAM implementation used. There are two variables that can be used to tweak the selection of the PAM implementation: PAM_DEFAULT is a user-settable variable whose value is the default PAM implementation to use. PAM_ACCEPTED is a package-settable list of PAM implementations that may be used by the package. Modify most packages that include PAM/buildlink3.mk to include pam.buildlink3.mk instead.
2005-01-14Rename the multiple inclusion guard to LINUX_PAM_BUILDLINK3_MK.jlam1-5/+5
2005-01-14* Rename the buildlink module name associated with the security/PAMjlam3-33/+45
package from "pam" to "linux-pam". * Rewrite PAM/builtin.mk to check that we have Linux-PAM, and re-classify MacOS X's PAM as Linux-PAM because it _is_, according to to Apple. Also don't use BUILDLINK_TRANSFORM.* to rewrite header file paths -- just use a symlink so that <security/*.h> can be used to find <pam/*.h>.
2005-01-13Note conflict with openpam-[0-9]*.jlam1-1/+3
2005-01-12BUILDLINK_TRANSFORM is not enough to buildlink the files when usingxtraeme1-1/+5
OpenPAM (NetBSD/FreeBSD), so use BUILDLINK_FILES to right directory.
2004-11-25PAM modules are dlopen'ed by the PAM library.jlam1-1/+3
2004-11-19Fix brokenness I introduced in the conversion of security/PAM to usejlam11-29/+50
libtool: the PAM libraries weren't being built with -DPAM_DYNAMIC, which made it impossible to dlopen PAM modules. Bump PKGREVISION.
2004-11-16Libtoolize security/PAM so that the appropriate options are passed tojlam16-168/+929
the compiler to build shared modules, and so that it builds correctly across different platforms. Bump the PKGREVISION. In particular, this should fix problems building this package on NetBSD/amd64.
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv1-2/+2
in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include.
2004-08-22Change the way that legacy USE_* and FOO_USE_* options are convertedjlam1-8/+3
into the bsd.options.mk framework. Instead of appending to ${PKG_OPTIONS_VAR}, it appends to PKG_DEFAULT_OPTIONS. This causes the default options to be the union of PKG_DEFAULT_OPTIONS and any old USE_* and FOO_USE_* settings. This fixes PR pkg/26590.
2004-08-19Whitespace nit.jlam1-2/+2
2004-08-12First cut at supporting the built-in PAM on MacOS X. It's not thejlam1-1/+20
same as Linux-PAM, but it's close enough for the purposes of compiling programs.
2004-08-06Reorder conditions so that if make does short-circuit boolean evalutation,jlam1-3/+3
then we avoid hitting the disk if we don't need to.
2004-08-06Accidentally reversed meaning of test.jlam1-2/+2
2004-08-06Redo previous to say what we really want: we don't care if ${LOCALBASE}jlam1-2/+7
is "/usr", what we really want to check is if the pam_appl.h header found is within the ${LOCALBASE} hierarchy, which implies that it's a pkgsrc-controlled file, and hence not built-in.
2004-08-06In the rare case when LOCALBASE is /usr, don't let this thinkreed1-2/+2
that /usr/include/security/pam_appl.h means that PAM is builtin. (This is so a dependency can be registered correctly.)
2004-08-05Document libcrack build option.jlam1-1/+4
2004-07-30Convert to use bsd.options.mk. The relevant options variable to setjlam1-3/+17
for each package can be determined by invoking: make show-var VARNAME=PKG_OPTIONS_VAR The old options are still supported unless the variable named in PKG_OPTIONS_VAR is set within make(1) (usually via /etc/mk.conf).
2004-07-06Accept "yes" or "YES" for USE_LIBCRACK.jlam1-2/+2
2004-05-17Garbage collect BUILDLINK_PKGBASE.<pkg> from buildlink3: it is not anymoreseb1-2/+1
used since revision 1.139 of mk/buildlink3/bsd.buildlink3.mk.
2004-05-11No longer used.snj1-74/+0
2004-05-11Remove support for buildlink2.snj1-7/+3
2004-03-29Match the template builtin.mk file in bsd.builtin.mk, and make the twojlam1-7/+2
packages that use builtin.mk files (graphics/xpm and pkgtools/x11-links) use the new format correctly.
2004-03-29Add a BUILDLINK_PKGBASE.<pkg> definition where it's not equal to <pkg>,jlam1-1/+2
e.g. "BUILDLINK_PKGBASE.gtk?= gtk+". This is mandated by the example buildlink[23].mk files in bsd.buildlink[23].mk.
2004-03-26Reverse the use of USE_DB185 in bdb.buildlink3.mk -- it defaults tojlam1-2/+1
"yes" and packages that can't use the DB-1.85 API should set it to "no". This makes the native DB the preferred DB if it exists.
2004-03-16If the ${PKGBASE} of a package doesn't match the token passed tojlam1-1/+2
BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
2004-03-10Convert to use bdb.buildlink3.mk.jlam1-2/+2
2004-03-10Split out the code that deals with checking whether the software isjlam2-45/+22
built-in or not into a separate builtin.mk file. The code to deal checking for built-in software is much simpler to deal with in pkgsrc. The buildlink3.mk file for a package will be of the usual format regardless of the package, which makes it simpler for packagers to update a package. The builtin.mk file for a package must define a single yes/no variable USE_BUILTIN.<pkg> that is used by bsd.buildlink3.mk to decide whether to use the built-in software or to use the pkgsrc software.
2004-02-18Reorder some lines so that BUILDLINK_USE_BUILTIN.<pkg> set in thejlam1-16/+18
environment overrides all other settings.
2004-02-12Create a new variable PREFER_NATIVE that has the opposite semanticsjlam2-6/+26
as PREFER_PKGSRC. Preferences are determined by the most specific instance of the package in either PREFER_PKGSRC or PREFER_NATIVE. If a package is specified in neither or in both variables, then PREFER_PKGSRC has precedence over PREFER_NATIVE.
2004-02-12Reorganize code so that any dependencies are checked as part of decidingjlam2-10/+14
whether the software is built-in or not. This facilitates implementing the forthcoming PKGSRC_NATIVE variable.
2004-02-05Make PREFER_PKGSRC just yes/no or a list of packages. This makes itjlam2-10/+6
simpler to understand.
2004-02-05Rename BUILDLINK_PREFER_PKGSRC to PREFER_PKGSRC so that we can use itsjlam2-10/+8
value outside of buildlink-related files.
2004-02-05Support a new global variable:jlam2-2/+18
BUILDLINK_PREFER_PKGSRC This variable determines whether or not to prefer the pkgsrc versions of software that is also present in the base system. This variable is multi-state: defined, or "yes" always prefer the pkgsrc versions not defined, or "no" only use the pkgsrc versions if needed by dependency requirements This can also take a list of packages for which to prefer the pkgsrc-installed software. The package names may be found by consulting the value added to BUILDLINK_PACKAGES in the buildlink[23].mk files for that package.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-17 23:17:27 +0000