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 whether 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, or in the case of --unmerge all atoms in a set will be
28 unmerged even if they are depended upon by other packages. This may change in
30 - sets can be referenced either in other file-based sets or as argument to emerge, but
31 not in ebuilds, config files or other tools at this time.
32 * "world" does no longer include "system" unconditionally, but you can add
33 "@system" to the worldfile to restore the old state.
36 ==================================
38 * Blockers are now resolved automatically in many more cases
39 than before. When it's safe, blocked packages are uninstalled
40 automatically so that users are no longer inconvenienced with the
41 task. Automatically uninstalled packages are displayed in the merge
42 list, marked "uninstall" and highlighted in red. With the --tree
43 option enabled, it's possible to see which package(s) caused other
44 ones to be automatically uninstalled.
46 * The metadata-transfer feature is now disabled by default. This disables the
47 "Updating Portage cache" routine that used to run at the tail end of each
48 `emerge --sync` operation. If you use something like the sqlite module and
49 want to keep all metadata in that format alone (useful for querying), enable
50 FEATURES="metadata-transfer" in make.conf. You should also enable
51 FEATURES="metadata-transfer" if you have any eclasses from PORTDIR_OVERLAY
52 that override eclasses from PORTDIR (in this case, you may have disabled
53 a relevant warning message by setting PORTAGE_ECLASS_WARNING_ENABLE="0" in
56 * The parallel-fetch feature is now enabled by default. It is optimized
57 to avoid doing redundant checksums for previously downloaded files that have
58 the correct size. Run `tail -f /var/log/emerge-fetch.log` in a
59 terminal to view parallel-fetch progress. Add FEATURES="-parallel-fetch"
60 to /etc/make.conf if you want to disable this feature.
62 * For extra careful dependency handling, emerge has a new --complete-graph
63 option that causes it to consider the deep dependencies of all packages from
64 the system and world sets. With this option enabled, emerge will bail out
65 if it determines that the given operation will break any dependencies of
66 the packages that have been added to the graph. Unlike the --deep option,
67 the --complete-graph option does not cause any more packages to be updated
68 than would have otherwise been updated with the option disabled.
71 ==================================
73 * If you have an overlay then you should remove **/files/digest-*
74 files (Manifest1) because they are no longer supported.
75 * If earlier versions of portage will be used to generate manifests
76 for your overlay then you should add a file named manifest1_obsolete
77 to the root of the repository in order to disable generation of the
78 Manifest1 digest files.
81 ==================================
83 * Visibility filtering is now supported for binary packages, so masking behavior
84 is essentially equivalent to that of ebuilds.
85 * There is no need to have a complete portage tree available when installing binary
86 packages or uninstalling packages, but a warning message will still be displayed if
87 it appears that a valid profile is not available.
88 * The emerge --search action supports searching of both installed and binary packages
89 The --usepkg and --usepkgonly options control which repositories are searched.
92 ==================================
94 * Portage now requires >=python-2.4, but doesn't need pycrypto anymore if
95 >=python-2.5 is installed and openssl supports the rmd160 hash.
96 * The "save_summary" and "echo" elog modules are now enabled by default. Setting
97 PORTAGE_ELOG_SYSTEM in make.conf will override this, so if you don't want elog
98 set PORTAGE_ELOG_SYSTEM="" in make.conf
99 * The unmerge process will remove any file that is not claimed by another
100 package in the same slot and is not protected by CONFIG_PROTECT, even if the
101 modification time or checksum differs from the file that was originally
102 installed. The old behavior is still available by adding -unmerge-orphans
104 * The world file now supports slot atoms such as 'sys-devel/gcc:3.4'. In some
105 cases, emerge --depclean may remove slots that it would not have removed
106 in the past. The emerge --noreplace command can be used to add an atom to the
107 world file and prevent matching packages from being removed. A slot atom
108 will be recorded in the world file for any atom that is precise enough to
109 identify a specific slot.
110 * For safer operation, emerge --prune will not unmerge packages that have
111 reverse dependencies. Use --verbose to display reverse dependencies. Use
112 --nodeps to completely ignore dependencies.
113 * emerge --depclean now accepts atoms and will unmerge only the specified
114 packages if nothing depends on them. Use --verbose to display reverse
118 ==================================
120 * Depending on the number of packages installed, users may notice a difference
121 in the time taken for dependency calculations. This performance penalty is
122 due to the addition of important new features which include the ability to
123 detect reverse blockers, the building of a complete dependency graph, and the
124 ability to use installed packages to satisify dependencies even after their
125 ebuilds have been removed from the portage tree.
126 * emerge does not necessarily update build time dependencies that are not
127 strictly required. See the --with-bdeps option in the emerge(1) man page.
130 ==================================
132 * emerge --search doesn't use regular expressions now anymore by default, so
133 emerge --search dvd+rw-tools now works as expected. Regular expressions can be enabled
134 by prefixing the search string with %.
135 * emerge --depclean algorithm is much safer than the old one.
136 * emerge --newuse detects changes in IUSE that previously went undetected.
139 ==================================
141 * new cache framework, breaking all old cache modules.
142 If you're having problems with portage_db_cdb, this is likely the cause.
143 * USE flag output ordering has changed. The old ordering is now an option
144 by the name of --alphabetical. Adding the option to EMERGE_DEFAULT_OPTS
145 in make.conf will restore the old behaviour permanently.
146 * The deprecated --inject has been removed, use /etc/portage/profile/package.provided
147 * The deprecated --upgradeonly has been removed, use /etc/portage/package.*
149 * 'emerge sync' has been deprecated, use 'emerge --sync' instead (same
151 * Tools that call emerge should override the EMERGE_DEFAULT_OPTS environment
152 variable or use the emerge --ignore-default-opts option.
153 * rsync option handling has been redesigned, instead of RSYNC_* variables
154 use PORTAGE_RSYNC_EXTRA_OPTS from now on.
155 * autouse (use.defaults) has been deprecated by specifying USE_ORDER in make.defaults
156 Users may still turn this back on by specifying USE_ORDER="env:pkg:conf:auto:defaults"
157 in make.conf. Interested in figuring out what use flags were turned off? Check out
158 /usr/portage/profiles/base/use.defaults and other use.defaults files that correspond