Rely on PYTHONPATH instead of PORTAGE_PYM_PATH for locating portage's python modules...

[portage.git] / NEWS

diff --git a/NEWS b/NEWS
index 630eb74f08ef596e15ffa0d1f6cc9d848b1af3e3..7f0bc40cce170246553b4006decab1be368e092b 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,11 +1,31 @@
 News (mainly features/major bug fixes)
 
+portage-2.1.2
+------------
+
+* ACCEPT_LICENSE and package.license allow packages with unaccepted licenses to
+  be masked.
+* Ebuilds support default USE flags via +flag in IUSE.
+* New-style virtuals are now usable for packages that depend on themselves for
+  bootstrap.
+* Profiles support multiple inheritance and package.use.
+* CONFIG_PROTECT and CONFIG_PROTECT_MASK both support files (not just
+  directories).
+* Collision protection handles symlinks properly.
+* Dependencies can be satisfied by installed packages that do not have matching
+  ebuilds in the portage tree or overlay.
+* Emerge automatically ignores blockers that are made irrelevant by an upgrade.
+* Emerge builds a complete dependency graph in order to ensure correct merge
+  order and detection of circular dependencies.
+* The world and system sets allow automatic update of all installed slots.
+* DEPEND atoms support SLOT dependencies of the form ${CATEGORY}/${PN}:${SLOT}.
+* Development: Extend PYTHONPATH support to allow overriding the hardcoded 
+  /usr/lib/portage/pym for development/testing purposes
+
 portage-2.1.1
 ------------
 
 * Profiles support use.force, package.use.force, and package.use.mask files.
-* New depclean algorithm is much safer than the old one.
-* Now emerge --newuse detects changes in IUSE that previously went undetected.
 
 portage-2.1 (ongoing via pre releases)
 ------------