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