1 Release Notes; upgrade information mainly.
2 Features/major bugfixes are listed in NEWS
5 ==================================
7 * The python namespace for portage has been sanitized, all portage related code
8 is now contained within the portage namespace. External script should be updated
9 accordingly, though links exist for backward compability.
10 * -* support in package.keywords was changed as it was inconsistent with
11 ACCEPT_KEYWORDS behavior (also see http://dev.gentoo.org/~genone/docs/KEYWORDS.stupid).
12 Previously having -* in package.keywords matched packages with KEYWORDS="-*",
13 now it resets the ACCEPT_KEYWORDS list for the given atom like it does when
14 used in ACCEPT_KEYWORDS.
15 For packages that don't specify any other KEYWORDS you can use the new ** token
16 as documented in portage(5) to disable KEYWORDS filtering completely.
17 * Portage now warns if a ebild repository does not have a name, as several new
18 features in 2.2 make use of or require named repositories. The repository name
19 is stored in profiles/repo_name in each repository.
22 ==================================
24 * The "save_summary" and "echo" elog modules are now enabled by default. Setting
25 PORTAGE_ELOG_SYSTEM in make.conf will override this, so if you don't want elog
26 set PORTAGE_ELOG_SYSTEM="" in make.conf
27 * The unmerge process will remove any file that is not claimed by another
28 package in the same slot and is not protected by CONFIG_PROTECT, even if the
29 modification time or checksum differs from the file that was originally
30 installed. The old behavior is still available by adding -unmerge-orphans
32 * The world file now supports slot atoms such as 'sys-devel/gcc:3.4'. In some
33 cases, emerge --depclean may remove slots that it would not have removed
34 in the past. The emerge --noreplace command can be used to add an atom to the
35 world file and prevent matching packages from being removed. A slot atom
36 will be recorded in the world file for any atom that is precise enough to
37 identify a specific slot.
40 ==================================
42 * Depending on the number of packages installed, users may notice a difference
43 in the time taken for dependency calculations. This performance penalty is
44 due to the addition of important new features which include the ability to
45 detect reverse blockers, the building of a complete dependency graph, and the
46 ability to use installed packages to satisify dependencies even after their
47 ebuilds have been removed from the portage tree.
48 * emerge does not necessarily update build time dependencies that are not
49 strictly required. See the --with-bdeps option in the emerge(1) man page.
52 ==================================
54 * emerge --search doesn't use regular expressions now anymore by default, so
55 emerge --search dvd+rw-tools now works as expected. Regular expressions can be enabled
56 by prefixing the search string with %.
57 * emerge --depclean algorithm is much safer than the old one.
58 * emerge --newuse detects changes in IUSE that previously went undetected.
61 ==================================
63 * new cache framework, breaking all old cache modules.
64 If you're having problems with portage_db_cdb, this is likely the cause.
65 * USE flag output ordering has changed. The old ordering is now an option
66 by the name of --alphabetical. Adding the option to EMERGE_DEFAULT_OPTS
67 in make.conf will restore the old behaviour permanently.
68 * The deprecated --inject has been removed, use /etc/portage/profile/package.provided
69 * The deprecated --upgradeonly has been removed, use /etc/portage/package.*
71 * 'emerge sync' has been deprecated, use 'emerge --sync' instead (same
73 * Tools that call emerge should override the EMERGE_DEFAULT_OPTS environment
74 variable or use the emerge --ignore-default-opts option.
75 * rsync option handling has been redesigned, instead of RSYNC_* variables
76 use PORTAGE_RSYNC_EXTRA_OPTS from now on.
77 * autouse (use.defaults) has been deprecated by specifying USE_ORDER in make.defaults
78 Users may still turn this back on by specifying USE_ORDER="env:pkg:conf:auto:defaults"
79 in make.conf. Interested in figuring out what use flags were turned off? Check out
80 /usr/portage/profiles/base/use.defaults and other use.defaults files that correspond