Next | Query returned 18 messages, browsing 11 to 20 | previous

History of commit frequency

CVS Commit History:


   2006-08-18 16:02:12 by Adrian Portelli | Files touched by this commit (4)
Log message:
Rename authtest to pam_dbm-authtest to avoid a conflict with authtest
 from the courier package.
   2006-03-04 22:31:14 by Johnny C. Lam | Files touched by this commit (2257)
Log message:
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to \ 
"pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
   2005-04-11 23:48:17 by Todd Vierling | Files touched by this commit (3539)
Log message:
Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.
   2005-02-24 14:10:14 by Alistair G. Crooks | Files touched by this commit (192)
Log message:
Add RMD160 digests.
   2005-01-14 06:15:40 by Johnny C. Lam | Files touched by this commit (15)
Log message:
Create a pam.buildlink3.mk file that is used by PAM-using packages.
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.
   2004-11-15 18:54:50 by Johnny C. Lam | Files touched by this commit (16)
Log message:
Rework the Berkeley DB detection in buildlink3:

  * Add a db1.builtin.mk file that detects whether DB-1.85 functionality
    exists in the base system, and remove the distinction between
    "native" and the other Berkeley DB packages -- we now refer to
    db[1234].  This paves the way for any future databases/db1 package.

  * USE_DB185 shouldn't need to be set by any packages -- its correct
    value is now automatically determined by bdb.buildlink3.mk depending
    on whether we explicitly request db1 or not.  By default, if you
    include bdb.buildlink3.mk, you want DB-1.85 functionality and
    USE_DB185 defaults to "yes", but if you explicitly remove db1 from
    the list of acceptable DBs, then USE_DB185 defaults to "no".

  * Set BDB_LIBS to the library options needed to link against the DB
    library when bdb.buildlink3.mk is included.

  * We only add the DB library to the linker command automatically if
    we want DB-1.85 functionality; otherwise assume that the package
    configure process can figure out how to probe for the correct
    headers and libraries.

Edit package Makefiles to nuke redundant settings of USE_DB185.
   2004-09-05 12:22:12 by grant beattie | Files touched by this commit (1)
Log message:
fix PKGNAME.
   2004-09-05 12:01:19 by grant beattie | Files touched by this commit (4) | Imported package
Log message:
Initial import of pam-dbm-0.2 into the NetBSD packages collection.

pam_dbm is a PAM module for DBM authentication.


Next | Query returned 18 messages, browsing 11 to 20 | previous