1 Release Notes; upgrade information mainly.
2 Features/major bugfixes are listed in NEWS
5 ==================================
7 * Portage now warns if an ebuild repository does not have a name, as several
8 new features in 2.2 make use of or require named repositories. The repository
9 name is stored in profiles/repo_name in each repository.
10 * Package set support: There are several important notes regarding package
12 - setnames have to be prefixed with @ (exceptions: 'world' and 'system' can
13 be used without the prefix)
14 - they may currently only include simple and versioned atoms or other sets,
15 use conditionals or any-of constructs aren't possible yet
16 - sets can be referenced either in other file-based sets or as argument to
17 emerge, but not in ebuilds, config files or other tools at this time.
18 - packages won't be unmerged if they are referenced by an installed package
19 set (with the exception of the world set, and installed being determined
20 by the world_sets file).
21 * "world" no longer includes "system" unconditionally, but you can add
22 "@system" to the world_sets file to restore the old state.
26 * Default behavior for emerge commands has changed so that packages are only
27 updated when necessary. In order to ensure that all packages are updated
28 when possible, you must now specify the -u/--update option. See bug #275945
29 for the rationale behind this change.
32 ==================================
33 * If you want overlay eclasses to override eclasses from other repos then see
34 the portage(5) man page for information about the new layout.conf and
35 repos.conf configuration files.
38 ==================================
40 * The default behavior has changed for `emerge world` and `emerge system`
41 commands. These commands will reinstall all packages from the given set
42 unless an option such as --noreplace, --update, or --newuse is specified.
43 * FEATURES=fixpackages is now enabled by default via make.globals. Set
44 FEATURES="-fixpackages" in make.conf if you'd like to disable it.
45 * File collision protection is now enabled by default via make.globals with
46 FEATURES=protect-owned. In order to protect files from be overwritten or
47 removed a inappropriate times, it is recommended to leave protect-owned
48 (or the similar collision-protect feature) enabled at all times. If you
49 want to disable collision protection completely (not recommended), then
50 you need to ensure that neither protect-owned nor collision-protect are
52 * The python namespace for portage has been sanitized, all portage related code
53 is now contained within the portage namespace. External script should be
54 updated accordingly, though links exist for backward compability.
55 * -* support in package.keywords was changed as it was inconsistent with
56 ACCEPT_KEYWORDS behavior (also see
57 http://dev.gentoo.org/~genone/docs/KEYWORDS.stupid).
58 Previously having -* in package.keywords matched packages with KEYWORDS="-*",
59 now it resets the ACCEPT_KEYWORDS list for the given atom like it does when
60 used in ACCEPT_KEYWORDS.
61 For packages that don't specify any other KEYWORDS you can use the new **
62 token as documented in portage(5) to disable KEYWORDS filtering completely.
63 * When generating manifests, existing distfiles digests will not be updated
64 in cases when the current file in $DISTDIR does not match. In order to
65 force digests to be updated, run `ebuild --force <ebuild file> manifest`.
66 This is a safety measure which protects valid distfiles digests from being
67 accidentally replaced by invalid digests.
68 * If you have overridden FETCHCOMMAND or RESUMECOMMAND variables, for
69 compatibility with EAPI 2, you must ensure that these variables are written
70 such that the downloaded file will be placed at \"\${DISTDIR}/\${FILE}\".
71 Refer to make.conf(5) for information about FETCHCOMMAND and RESUMECOMMAND.
74 ==================================
76 * The pkg_postinst phase is now called after the previous version of a
77 package has been removed. As a consequence, it is no longer possible
78 to call has_version in pkg_postinst to detect whether the current
79 install operation is an upgrade or downgrade. If this information is
80 needed during the pkg_postinst phase, do the has_version call in an
81 earlier phase (such as pkg_preinst) and store the result in a global
82 variable to be accessed by pkg_postinst when it is called. Bug #226505
83 tracks all issues related to this phase execution order change.
84 * The metadata-transfer feature is now disabled by default. This disables the
85 "Updating Portage cache" routine that used to run at the tail end of each
86 `emerge --sync` operation. If you use something like the sqlite module and
87 want to keep all metadata in that format alone (useful for querying), enable
88 FEATURES="metadata-transfer" in make.conf. You should also enable
89 FEATURES="metadata-transfer" if you have any eclasses from PORTDIR_OVERLAY
90 that override eclasses from PORTDIR (in this case, you may have disabled
91 a relevant warning message by setting PORTAGE_ECLASS_WARNING_ENABLE="0" in
93 * The parallel-fetch feature is now enabled by default. It is optimized
94 to avoid doing redundant checksums for previously downloaded files that have
95 the correct size. Run `tail -f /var/log/emerge-fetch.log` in a
96 terminal to view parallel-fetch progress. Add FEATURES="-parallel-fetch"
97 to /etc/make.conf if you want to disable this feature.
100 ==================================
102 * If you have an overlay then you should remove **/files/digest-*
103 files (Manifest1) because they are no longer supported.
104 * If earlier versions of portage will be used to generate manifests
105 for your overlay then you should add a file named manifest1_obsolete
106 to the root of the repository in order to disable generation of the
107 Manifest1 digest files.
110 ==================================
112 * Visibility filtering is now supported for binary packages, so masking behavior
113 is essentially equivalent to that of ebuilds.
114 * There is no need to have a complete portage tree available when installing binary
115 packages or uninstalling packages, but a warning message will still be displayed if
116 it appears that a valid profile is not available.
119 ==================================
121 * Portage now requires >=python-2.4, but doesn't need pycrypto anymore if
122 >=python-2.5 is installed and openssl supports the rmd160 hash.
123 * The "save_summary" and "echo" elog modules are now enabled by default. Setting
124 PORTAGE_ELOG_SYSTEM in make.conf will override this, so if you don't want elog
125 set PORTAGE_ELOG_SYSTEM="" in make.conf
126 * The unmerge process will remove any file that is not claimed by another
127 package in the same slot and is not protected by CONFIG_PROTECT, even if the
128 modification time or checksum differs from the file that was originally
129 installed. The old behavior is still available by adding -unmerge-orphans
131 * The world file now supports slot atoms such as 'sys-devel/gcc:3.4'. In some
132 cases, emerge --depclean may remove slots that it would not have removed
133 in the past. The emerge --noreplace command can be used to add an atom to the
134 world file and prevent matching packages from being removed. A slot atom
135 will be recorded in the world file for any atom that is precise enough to
136 identify a specific slot.
137 * For safer operation, emerge --prune will not unmerge packages that have
138 reverse dependencies. Use --verbose to display reverse dependencies. Use
139 --nodeps to completely ignore dependencies.
140 * emerge --depclean now accepts atoms and will unmerge only the specified
141 packages if nothing depends on them. Use --verbose to display reverse
145 ==================================
147 * Depending on the number of packages installed, users may notice a difference
148 in the time taken for dependency calculations. This performance penalty is
149 due to the addition of important new features which include the ability to
150 detect reverse blockers, the building of a complete dependency graph, and the
151 ability to use installed packages to satisify dependencies even after their
152 ebuilds have been removed from the portage tree.
153 * emerge does not necessarily update build time dependencies that are not
154 strictly required. See the --with-bdeps option in the emerge(1) man page.
157 ==================================
159 * emerge --search doesn't use regular expressions now anymore by default, so
160 emerge --search dvd+rw-tools now works as expected. Regular expressions can be enabled
161 by prefixing the search string with %.
162 * emerge --depclean algorithm is much safer than the old one.
163 * emerge --newuse detects changes in IUSE that previously went undetected.
166 ==================================
168 * new cache framework, breaking all old cache modules.
169 If you're having problems with portage_db_cdb, this is likely the cause.
170 * USE flag output ordering has changed. The old ordering is now an option
171 by the name of --alphabetical. Adding the option to EMERGE_DEFAULT_OPTS
172 in make.conf will restore the old behaviour permanently.
173 * The deprecated --inject has been removed, use /etc/portage/profile/package.provided
174 * The deprecated --upgradeonly has been removed, use /etc/portage/package.*
176 * 'emerge sync' has been deprecated, use 'emerge --sync' instead (same
178 * Tools that call emerge should override the EMERGE_DEFAULT_OPTS environment
179 variable or use the emerge --ignore-default-opts option.
180 * rsync option handling has been redesigned, instead of RSYNC_* variables
181 use PORTAGE_RSYNC_EXTRA_OPTS from now on.
182 * autouse (use.defaults) has been deprecated by specifying USE_ORDER in make.defaults
183 Users may still turn this back on by specifying USE_ORDER="env:pkg:conf:auto:defaults"
184 in make.conf. Interested in figuring out what use flags were turned off? Check out
185 /usr/portage/profiles/base/use.defaults and other use.defaults files that correspond