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 - they may currently only include simple and versioned atoms or other sets,
13 use conditionals or any-of constructs aren't possible yet
14 - sets can be referenced either in other file-based sets or as argument to
15 emerge, but not in ebuilds, config files or other tools at this time.
16 - packages won't be unmerged if they are referenced by an installed package
17 set (with the exception of the world set, and installed being determined
18 by the world_sets file).
19 * The "selected" package set, which includes packages listed in
20 /var/lib/portage/world, has been extended to include nested sets that may
21 be listed /var/lib/portage/world_sets.
24 ==================================
25 * User-defined package sets can now be created by placing files in the
26 /etc/portage/sets/ directory. Refer to the emerge(1) and portage(5) man
27 pages for more information.
30 ==================================
31 * FEATURES=config-protect-if-modified is now enabled by default. This causes
32 the CONFIG_PROTECT behavior to be skipped for files that have not been
33 modified since they were installed.
36 ==================================
37 * FEATURES=fixpackages is now enabled unconditionally. Set --package-moves=n
38 in EMERGE_DEFAULT_OPTS if you need to temporarily avoid package moves for
42 ==================================
43 * The emerge --autounmask option is now enabled by default. The
44 --autounmask-write option can be used to have config changes automatically
45 written to the appropriate files (respecting --ask and CONFIG_PROTECT). If
46 --autounmask behavior is not desired as the default behavior, then it can
47 be disabled by adding --autounmask=n to the EMERGE_DEFAULT_OPTS variable in
48 make.conf. Refer to the emerge(1) man page for more information.
51 ==================================
52 * The emerge "world" set now includes separate "selected" and "system" sets,
53 where the "selected" set includes packages listed in /var/lib/portage/world.
54 * Package set names in emerge arguments have to be prefixed with @ (exceptions:
55 'world' and 'system' can be used without the prefix).
56 * Configuration files now support atoms with wildcards inside the category and
57 package name parts of the atoms.
58 * The functionality of the autounmask program is emulated by the new emerge
59 --autounmask option, which outputs required configuration changes for
60 package.accept_keywords and package.use.
61 * The new emerge --exclude option allows packages to be excluded from the
62 dependency resolution. Doing so might result in a fatal error. See the
63 emerge(1) man page for details.
64 * Per-package environment variables can be set with the new package.env
65 configuration file in /etc/portage/. See the portage(5) man page for details.
66 * Support for per-package bashrc files in /etc/portage/env. See the portage(5)
68 * The package.keywords configuration file in /etc/portage/ is now deprecated.
69 Instead use the package.accept_keywords file which has the same format and
70 behavior. See the portage(5) man page for details.
71 * FEATURES="fixlafiles" (enabled by default): Rewrites newly installed .la
72 files in the same way dev-util/lafilefixer does. Note that this won't fix
73 your installed .la files.
76 ==================================
77 * The new --rebuilt-binaries option will replace installed packages with binary
78 packages that have been rebuilt. Rebuilds are detected by comparison of
79 BUILD_TIME package metadata. This option is enabled automatically when using
80 binary packages (--usepkgonly or --getbinpkgonly) together with --update and
84 ==================================
85 * Default behavior for emerge commands has changed so that packages are only
86 updated when necessary. In order to ensure that all packages are updated
87 when possible, you must now specify the -u/--update option. See bug #275945
88 for the rationale behind this change.
89 * If using python3, you may notice that some types of program output which
90 require a tty device (like the wget progress bar) will be disabled. This
91 is due to an upstream python issue: http://bugs.python.org/issue5380. See
92 bug #287648 for more information.
93 * Licenses in the @EULA license group are now masked by the default
94 ACCEPT_LICENSE setting. You can unmask all licenses by setting
95 ACCEPT_LICENSE="*" in /etc/make.conf. See the make.conf(5) man page for
96 more information about ACCEPT_LICENSE.
99 ==================================
100 * If you want overlay eclasses to override eclasses from other repos then see
101 the portage(5) man page for information about the new layout.conf and
102 repos.conf configuration files.
105 ==================================
107 * The default behavior has changed for `emerge world` and `emerge system`
108 commands. These commands will reinstall all packages from the given set
109 unless an option such as --noreplace, --update, or --newuse is specified.
110 * FEATURES=fixpackages is now enabled by default via make.globals. Set
111 FEATURES="-fixpackages" in make.conf if you'd like to disable it.
112 * File collision protection is now enabled by default via make.globals with
113 FEATURES=protect-owned. In order to protect files from be overwritten or
114 removed a inappropriate times, it is recommended to leave protect-owned
115 (or the similar collision-protect feature) enabled at all times. If you
116 want to disable collision protection completely (not recommended), then
117 you need to ensure that neither protect-owned nor collision-protect are
119 * The python namespace for portage has been sanitized, all portage related code
120 is now contained within the portage namespace. External script should be
121 updated accordingly, though links exist for backward compability.
122 * -* support in package.keywords was changed as it was inconsistent with
123 ACCEPT_KEYWORDS behavior (also see
124 http://dev.gentoo.org/~genone/docs/KEYWORDS.stupid).
125 Previously having -* in package.keywords matched packages with KEYWORDS="-*",
126 now it resets the ACCEPT_KEYWORDS list for the given atom like it does when
127 used in ACCEPT_KEYWORDS.
128 For packages that don't specify any other KEYWORDS you can use the new **
129 token as documented in portage(5) to disable KEYWORDS filtering completely.
130 * When generating manifests, existing distfiles digests will not be updated
131 in cases when the current file in $DISTDIR does not match. In order to
132 force digests to be updated, run `ebuild --force <ebuild file> manifest`.
133 This is a safety measure which protects valid distfiles digests from being
134 accidentally replaced by invalid digests.
135 * If you have overridden FETCHCOMMAND or RESUMECOMMAND variables, for
136 compatibility with EAPI 2, you must ensure that these variables are written
137 such that the downloaded file will be placed at \"\${DISTDIR}/\${FILE}\".
138 Refer to make.conf(5) for information about FETCHCOMMAND and RESUMECOMMAND.
141 ==================================
143 * The pkg_postinst phase is now called after the previous version of a
144 package has been removed. As a consequence, it is no longer possible
145 to call has_version in pkg_postinst to detect whether the current
146 install operation is an upgrade or downgrade. If this information is
147 needed during the pkg_postinst phase, do the has_version call in an
148 earlier phase (such as pkg_preinst) and store the result in a global
149 variable to be accessed by pkg_postinst when it is called. Bug #226505
150 tracks all issues related to this phase execution order change.
151 * The metadata-transfer feature is now disabled by default. This disables the
152 "Updating Portage cache" routine that used to run at the tail end of each
153 `emerge --sync` operation. If you use something like the sqlite module and
154 want to keep all metadata in that format alone (useful for querying), enable
155 FEATURES="metadata-transfer" in make.conf. You should also enable
156 FEATURES="metadata-transfer" if you have any eclasses from PORTDIR_OVERLAY
157 that override eclasses from PORTDIR (in this case, you may have disabled
158 a relevant warning message by setting PORTAGE_ECLASS_WARNING_ENABLE="0" in
160 * The parallel-fetch feature is now enabled by default. It is optimized
161 to avoid doing redundant checksums for previously downloaded files that have
162 the correct size. Run `tail -f /var/log/emerge-fetch.log` in a
163 terminal to view parallel-fetch progress. Add FEATURES="-parallel-fetch"
164 to /etc/make.conf if you want to disable this feature.
167 ==================================
169 * If you have an overlay then you should remove **/files/digest-*
170 files (Manifest1) because they are no longer supported.
171 * If earlier versions of portage will be used to generate manifests
172 for your overlay then you should add a file named manifest1_obsolete
173 to the root of the repository in order to disable generation of the
174 Manifest1 digest files.
177 ==================================
179 * Visibility filtering is now supported for binary packages, so masking behavior
180 is essentially equivalent to that of ebuilds.
181 * There is no need to have a complete portage tree available when installing binary
182 packages or uninstalling packages, but a warning message will still be displayed if
183 it appears that a valid profile is not available.
186 ==================================
188 * Portage now requires >=python-2.4, but doesn't need pycrypto anymore if
189 >=python-2.5 is installed and openssl supports the rmd160 hash.
190 * The "save_summary" and "echo" elog modules are now enabled by default. Setting
191 PORTAGE_ELOG_SYSTEM in make.conf will override this, so if you don't want elog
192 set PORTAGE_ELOG_SYSTEM="" in make.conf
193 * The unmerge process will remove any file that is not claimed by another
194 package in the same slot and is not protected by CONFIG_PROTECT, even if the
195 modification time or checksum differs from the file that was originally
196 installed. The old behavior is still available by adding -unmerge-orphans
198 * The world file now supports slot atoms such as 'sys-devel/gcc:3.4'. In some
199 cases, emerge --depclean may remove slots that it would not have removed
200 in the past. The emerge --noreplace command can be used to add an atom to the
201 world file and prevent matching packages from being removed. A slot atom
202 will be recorded in the world file for any atom that is precise enough to
203 identify a specific slot.
204 * For safer operation, emerge --prune will not unmerge packages that have
205 reverse dependencies. Use --verbose to display reverse dependencies. Use
206 --nodeps to completely ignore dependencies.
207 * emerge --depclean now accepts atoms and will unmerge only the specified
208 packages if nothing depends on them. Use --verbose to display reverse
212 ==================================
214 * Depending on the number of packages installed, users may notice a difference
215 in the time taken for dependency calculations. This performance penalty is
216 due to the addition of important new features which include the ability to
217 detect reverse blockers, the building of a complete dependency graph, and the
218 ability to use installed packages to satisify dependencies even after their
219 ebuilds have been removed from the portage tree.
220 * emerge does not necessarily update build time dependencies that are not
221 strictly required. See the --with-bdeps option in the emerge(1) man page.
224 ==================================
226 * emerge --search doesn't use regular expressions now anymore by default, so
227 emerge --search dvd+rw-tools now works as expected. Regular expressions can be enabled
228 by prefixing the search string with %.
229 * emerge --depclean algorithm is much safer than the old one.
230 * emerge --newuse detects changes in IUSE that previously went undetected.
233 ==================================
235 * new cache framework, breaking all old cache modules.
236 If you're having problems with portage_db_cdb, this is likely the cause.
237 * USE flag output ordering has changed. The old ordering is now an option
238 by the name of --alphabetical. Adding the option to EMERGE_DEFAULT_OPTS
239 in make.conf will restore the old behaviour permanently.
240 * The deprecated --inject has been removed, use /etc/portage/profile/package.provided
241 * The deprecated --upgradeonly has been removed, use /etc/portage/package.*
243 * 'emerge sync' has been deprecated, use 'emerge --sync' instead (same
245 * Tools that call emerge should override the EMERGE_DEFAULT_OPTS environment
246 variable or use the emerge --ignore-default-opts option.
247 * rsync option handling has been redesigned, instead of RSYNC_* variables
248 use PORTAGE_RSYNC_EXTRA_OPTS from now on.
249 * autouse (use.defaults) has been deprecated by specifying USE_ORDER in make.defaults
250 Users may still turn this back on by specifying USE_ORDER="env:pkg:conf:auto:defaults"
251 in make.conf. Interested in figuring out what use flags were turned off? Check out
252 /usr/portage/profiles/base/use.defaults and other use.defaults files that correspond