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 an ebuild 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.
20 * Package set support: There are several important notes regarding package sets:
21 - setnames have to be prefixed with @ (exceptions: 'world' and 'system' can be
22 used without the prefix)
23 - they may currently only include simple and versioned atoms or other sets, use
24 conditionals or any-of constructs aren't possible yet
25 - emerge makes no difference atm wether you pass a setname or all atoms contained
26 in the set to it, this means that without options packages will be remerged if
27 already installed and added to the worldfile, or in the case of --unmerge all
28 atoms in a set will be unmerged even if they are depended upon by other
32 ==================================
34 * Visibility filtering is now supported for binary packages, so masking behavior
35 is essentially equivalent to that of ebuilds.
36 * There is no need to have a complete portage tree available when installing binary
37 packages or uninstalling packages, but a warning message will still be displayed if
38 it appears that a valid profile is not available.
39 * The emerge --search action supports searching of both installed and binary packages
40 The --usepkg and --usepkgonly options control which repositories are searched.
43 ==================================
45 * Portage now requires >=python-2.4, but doesn't need pycrypto anymore if
46 >=python-2.5 is installed and openssl supports the rmd160 hash.
47 * The "save_summary" and "echo" elog modules are now enabled by default. Setting
48 PORTAGE_ELOG_SYSTEM in make.conf will override this, so if you don't want elog
49 set PORTAGE_ELOG_SYSTEM="" in make.conf
50 * The unmerge process will remove any file that is not claimed by another
51 package in the same slot and is not protected by CONFIG_PROTECT, even if the
52 modification time or checksum differs from the file that was originally
53 installed. The old behavior is still available by adding -unmerge-orphans
55 * The world file now supports slot atoms such as 'sys-devel/gcc:3.4'. In some
56 cases, emerge --depclean may remove slots that it would not have removed
57 in the past. The emerge --noreplace command can be used to add an atom to the
58 world file and prevent matching packages from being removed. A slot atom
59 will be recorded in the world file for any atom that is precise enough to
60 identify a specific slot.
61 * For safer operation, emerge --prune will not unmerge packages that have
62 reverse dependencies. Use --verbose to display reverse dependencies. Use
63 --nodeps to completely ignore dependencies.
64 * emerge --depclean now accepts atoms and will unmerge only the specified
65 packages if nothing depends on them. Use --verbose to display reverse
69 ==================================
71 * Depending on the number of packages installed, users may notice a difference
72 in the time taken for dependency calculations. This performance penalty is
73 due to the addition of important new features which include the ability to
74 detect reverse blockers, the building of a complete dependency graph, and the
75 ability to use installed packages to satisify dependencies even after their
76 ebuilds have been removed from the portage tree.
77 * emerge does not necessarily update build time dependencies that are not
78 strictly required. See the --with-bdeps option in the emerge(1) man page.
81 ==================================
83 * emerge --search doesn't use regular expressions now anymore by default, so
84 emerge --search dvd+rw-tools now works as expected. Regular expressions can be enabled
85 by prefixing the search string with %.
86 * emerge --depclean algorithm is much safer than the old one.
87 * emerge --newuse detects changes in IUSE that previously went undetected.
90 ==================================
92 * new cache framework, breaking all old cache modules.
93 If you're having problems with portage_db_cdb, this is likely the cause.
94 * USE flag output ordering has changed. The old ordering is now an option
95 by the name of --alphabetical. Adding the option to EMERGE_DEFAULT_OPTS
96 in make.conf will restore the old behaviour permanently.
97 * The deprecated --inject has been removed, use /etc/portage/profile/package.provided
98 * The deprecated --upgradeonly has been removed, use /etc/portage/package.*
100 * 'emerge sync' has been deprecated, use 'emerge --sync' instead (same
102 * Tools that call emerge should override the EMERGE_DEFAULT_OPTS environment
103 variable or use the emerge --ignore-default-opts option.
104 * rsync option handling has been redesigned, instead of RSYNC_* variables
105 use PORTAGE_RSYNC_EXTRA_OPTS from now on.
106 * autouse (use.defaults) has been deprecated by specifying USE_ORDER in make.defaults
107 Users may still turn this back on by specifying USE_ORDER="env:pkg:conf:auto:defaults"
108 in make.conf. Interested in figuring out what use flags were turned off? Check out
109 /usr/portage/profiles/base/use.defaults and other use.defaults files that correspond