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