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