<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pkgsrc/security/PAM/module.mk, branch cube-native-xorg</title>
<subtitle>[no description]</subtitle>
<id>https://git.osdyson.ru/mirror/pkgsrc/atom?h=cube-native-xorg</id>
<link rel='self' href='https://git.osdyson.ru/mirror/pkgsrc/atom?h=cube-native-xorg'/>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/'/>
<updated>2005-03-24T22:42:58Z</updated>
<entry>
<title>Don't check for USE_BUILDLINK3 anymore in these files.  These are included</title>
<updated>2005-03-24T22:42:58Z</updated>
<author>
<name>jlam</name>
<email>jlam@pkgsrc.org</email>
</author>
<published>2005-03-24T22:42:58Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=da2fc8539087dd463808a7a952672f18f079609b'/>
<id>urn:sha1:da2fc8539087dd463808a7a952672f18f079609b</id>
<content type='text'>
by other package Makefiles, and with the deprecation of USE_BUILDLINK3
support in the infrastructure files, these had the potential to break
existing packages.</content>
</entry>
<entry>
<title>Create a pam.buildlink3.mk file that is used by PAM-using packages.</title>
<updated>2005-01-14T05:15:39Z</updated>
<author>
<name>jlam</name>
<email>jlam@pkgsrc.org</email>
</author>
<published>2005-01-14T05:15:39Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=1b5734f517b624ae847f6133a3f35f4f2f355ed3'/>
<id>urn:sha1:1b5734f517b624ae847f6133a3f35f4f2f355ed3</id>
<content type='text'>
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.</content>
</entry>
<entry>
<title>* Rename the buildlink module name associated with the security/PAM</title>
<updated>2005-01-14T00:08:46Z</updated>
<author>
<name>jlam</name>
<email>jlam@pkgsrc.org</email>
</author>
<published>2005-01-14T00:08:46Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=c8dd0743a82b2de97126e7a6bb78bb59d1a33172'/>
<id>urn:sha1:c8dd0743a82b2de97126e7a6bb78bb59d1a33172</id>
<content type='text'>
  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 &lt;security/*.h&gt; can be used to find
  &lt;pam/*.h&gt;.</content>
</entry>
<entry>
<title>Remove support for buildlink2.</title>
<updated>2004-05-11T04:39:03Z</updated>
<author>
<name>snj</name>
<email>snj@pkgsrc.org</email>
</author>
<published>2004-05-11T04:39:03Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=0350fb16cc16c0752f6b1798dcdc42af970bdec5'/>
<id>urn:sha1:0350fb16cc16c0752f6b1798dcdc42af970bdec5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>First cut at a common module.mk file to be included by PAM module packages.</title>
<updated>2004-01-08T00:08:23Z</updated>
<author>
<name>jlam</name>
<email>jlam@pkgsrc.org</email>
</author>
<published>2004-01-08T00:08:23Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=3d57ea1af7f25a851fdbd2f50b5412a5688678ee'/>
<id>urn:sha1:3d57ea1af7f25a851fdbd2f50b5412a5688678ee</id>
<content type='text'>
</content>
</entry>
</feed>
