2.1.4_rc3 bump. This version adds support for persistence of colon
separated SANDBOX_{DENY,READ,PREDICT,WRITE} variables between phases
so things like the global scope addpredict() call in qt3.eclass will
continue to work.
(Portage version: 2.1.4_rc3)
(Signed Manifest commit)

2.1.4_rc3 bump. This version adds support for persistence of colon
separated SANDBOX_{DENY,READ,PREDICT,WRITE} variables between phases
so things like the global scope addpredict() call in qt3.eclass will
continue to work.
(Portage version: 2.1.4_rc3)

2.1.4_rc2 bump. This version makes the bashrc behavior in the ebuild
environment more compatible with older versions of portage. Now the
full environment will be available to the bashrc like it used to be,
which solves an issue with grep hanging indefinitely in
default-bsd/profile.bashrc.
(Portage version: 2.1.4_rc2)
(Signed Manifest commit)

2.1.4_rc2 bump. This version makes the bashrc behavior in the ebuild
environment more compatible with older versions of portage. Now the
full environment will be available to the bashrc like it used to be,
which solves an issue with grep hanging indefinitely in
default-bsd/profile.bashrc.
(Portage version: 2.1.4_rc2)

2.1.4_rc1. This fixes bugs #46223, #190128, #198398, #198491, #198492,
and #199311. This release includes new environment processing support
which solves bugs #46223 and #190128. Now an ebuild and it's eclasses
are only sourced once, and the resulting bash environment is reused for
the entire lifecycle of the package. This allows eclasses to have
incompatible api changes or be completely removed from the tree without
causing problems for installed packages. It also allows environment
variables to persist through the entire lifecycle of a package. For
example, a binary package has access to the build time environment, and
a package being uninstalled has access to the build time and install
time environments. Bug #200044 tracks all bugs fixed since 2.1.3.x.
(Portage version: 2.1.4_rc1)
(Signed Manifest commit)

2.1.4_rc1. This fixes bugs #46223, #190128, #198398, #198491, #198492,
and #199311. This release includes new environment processing support
which solves bugs #46223 and #190128. Now an ebuild and it's eclasses
are only sourced once, and the resulting bash environment is reused for
the entire lifecycle of the package. This allows eclasses to have
incompatible api changes or be completely removed from the tree without
causing problems for installed packages. It also allows environment
variables to persist through the entire lifecycle of a package. For
example, a binary package has access to the build time environment, and
a package being uninstalled has access to the build time and install
time environments. Bug #200044 tracks all bugs fixed since 2.1.3.x.
(Portage version: 2.1.4_rc1)

2.1.3.19 bump. This fixes world file issues with USE=multislot packages
as reported in bug #198129 and also removes the usage.obsolete warning
about KEYWORDS containing -* since people are using -* to indicate that
a package should not be tried on archs other than those for which it
already has KEYWORDS. Bug #198097 tracks all bugs fixed since 2.1.3.16.

2.1.3.19 bump. This fixes world file issues with USE=multislot packages
as reported in bug #198129 and also removes the usage.obsolete warning
about KEYWORDS containing -* since people are using -* to indicate that
a package should not be tried on archs other than those for which it
already has KEYWORDS. Bug #198097 tracks all bugs fixed since 2.1.3.16.

PAM support updates: change the dependency back to sys-libs/pam but ask for at least version 0.99 (so that we know we have the proper pam_tally, and we can drop some conditionals), OpenPAM wouldn't work for shadow for now. Simplify the pam.d installation, without using the for loop and case statement. Use the 'epam syntax' for the selinux conditional. Update the options passed to pam_tally so that they don't throw warnings when used with Linux-PAM 0.99.
(Portage version: 2.1.3.17)
(Signed Manifest commit)

PAM support updates: change the dependency back to sys-libs/pam but ask for at least version 0.99 (so that we know we have the proper pam_tally, and we can drop some conditionals), OpenPAM wouldn't work for shadow for now. Simplify the pam.d installation, without using the for loop and case statement. Use the 'epam syntax' for the selinux conditional. Update the options passed to pam_tally so that they don't throw warnings when used with Linux-PAM 0.99.
(Portage version: 2.1.3.17)