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" does no longer include "system" unconditionally, but you can add
22 "@system" to the world_sets file to restore the old state.
25 ==================================
27 * The default behavior has changed for `emerge world` and `emerge system`
28 commands. These commands will reinstall all packages from the given set
29 unless an option such as --noreplace, --update, or --newuse is specified.
30 * FEATURES=fixpackages is now enabled by default via make.globals. Set
31 FEATURES="-fixpackages" in make.conf if you'd like to disable it.
32 * File collision protection is now enabled by default via make.globals with
33 FEATURES=protect-owned. In order to protect files from be overwritten or
34 removed a inappropriate times, it is recommended to leave protect-owned
35 (or the similar collision-protect feature) enabled at all times. If you
36 want to disable collision protection completely (not recommended), then
37 you need to ensure that neither protect-owned nor collision-protect are
39 * The python namespace for portage has been sanitized, all portage related code
40 is now contained within the portage namespace. External script should be
41 updated accordingly, though links exist for backward compability.
42 * -* support in package.keywords was changed as it was inconsistent with
43 ACCEPT_KEYWORDS behavior (also see
44 http://dev.gentoo.org/~genone/docs/KEYWORDS.stupid).
45 Previously having -* in package.keywords matched packages with KEYWORDS="-*",
46 now it resets the ACCEPT_KEYWORDS list for the given atom like it does when
47 used in ACCEPT_KEYWORDS.
48 For packages that don't specify any other KEYWORDS you can use the new **
49 token as documented in portage(5) to disable KEYWORDS filtering completely.
50 * When generating manifests, existing distfiles digests will not be updated
51 in cases when the current file in $DISTDIR does not match. In order to
52 force digests to be updated, run `ebuild --force <ebuild file> manifest`.
53 This is a safety measure which protects valid distfiles digests from being
54 accidentally replaced by invalid digests.
57 ==================================
59 * The pkg_postinst phase is now called after the previous version of a
60 package has been removed. As a consequence, it is no longer possible
61 to call has_version in pkg_postinst to detect whether the current
62 install operation is an upgrade or downgrade. If this information is
63 needed during the pkg_postinst phase, do the has_version call in an
64 earlier phase (such as pkg_preinst) and store the result in a global
65 variable to be accessed by pkg_postinst when it is called. Bug #226505
66 tracks all issues related to this phase execution order change.
67 * The metadata-transfer feature is now disabled by default. This disables the
68 "Updating Portage cache" routine that used to run at the tail end of each
69 `emerge --sync` operation. If you use something like the sqlite module and
70 want to keep all metadata in that format alone (useful for querying), enable
71 FEATURES="metadata-transfer" in make.conf. You should also enable
72 FEATURES="metadata-transfer" if you have any eclasses from PORTDIR_OVERLAY
73 that override eclasses from PORTDIR (in this case, you may have disabled
74 a relevant warning message by setting PORTAGE_ECLASS_WARNING_ENABLE="0" in
76 * The parallel-fetch feature is now enabled by default. It is optimized
77 to avoid doing redundant checksums for previously downloaded files that have
78 the correct size. Run `tail -f /var/log/emerge-fetch.log` in a
79 terminal to view parallel-fetch progress. Add FEATURES="-parallel-fetch"
80 to /etc/make.conf if you want to disable this feature.
83 ==================================
85 * If you have an overlay then you should remove **/files/digest-*
86 files (Manifest1) because they are no longer supported.
87 * If earlier versions of portage will be used to generate manifests
88 for your overlay then you should add a file named manifest1_obsolete
89 to the root of the repository in order to disable generation of the
90 Manifest1 digest files.
93 ==================================
95 * Visibility filtering is now supported for binary packages, so masking behavior
96 is essentially equivalent to that of ebuilds.
97 * There is no need to have a complete portage tree available when installing binary
98 packages or uninstalling packages, but a warning message will still be displayed if
99 it appears that a valid profile is not available.
102 ==================================
104 * Portage now requires >=python-2.4, but doesn't need pycrypto anymore if
105 >=python-2.5 is installed and openssl supports the rmd160 hash.
106 * The "save_summary" and "echo" elog modules are now enabled by default. Setting
107 PORTAGE_ELOG_SYSTEM in make.conf will override this, so if you don't want elog
108 set PORTAGE_ELOG_SYSTEM="" in make.conf
109 * The unmerge process will remove any file that is not claimed by another
110 package in the same slot and is not protected by CONFIG_PROTECT, even if the
111 modification time or checksum differs from the file that was originally
112 installed. The old behavior is still available by adding -unmerge-orphans
114 * The world file now supports slot atoms such as 'sys-devel/gcc:3.4'. In some
115 cases, emerge --depclean may remove slots that it would not have removed
116 in the past. The emerge --noreplace command can be used to add an atom to the
117 world file and prevent matching packages from being removed. A slot atom
118 will be recorded in the world file for any atom that is precise enough to
119 identify a specific slot.
120 * For safer operation, emerge --prune will not unmerge packages that have
121 reverse dependencies. Use --verbose to display reverse dependencies. Use
122 --nodeps to completely ignore dependencies.
123 * emerge --depclean now accepts atoms and will unmerge only the specified
124 packages if nothing depends on them. Use --verbose to display reverse
128 ==================================
130 * Depending on the number of packages installed, users may notice a difference
131 in the time taken for dependency calculations. This performance penalty is
132 due to the addition of important new features which include the ability to
133 detect reverse blockers, the building of a complete dependency graph, and the
134 ability to use installed packages to satisify dependencies even after their
135 ebuilds have been removed from the portage tree.
136 * emerge does not necessarily update build time dependencies that are not
137 strictly required. See the --with-bdeps option in the emerge(1) man page.
140 ==================================
142 * emerge --search doesn't use regular expressions now anymore by default, so
143 emerge --search dvd+rw-tools now works as expected. Regular expressions can be enabled
144 by prefixing the search string with %.
145 * emerge --depclean algorithm is much safer than the old one.
146 * emerge --newuse detects changes in IUSE that previously went undetected.
149 ==================================
151 * new cache framework, breaking all old cache modules.
152 If you're having problems with portage_db_cdb, this is likely the cause.
153 * USE flag output ordering has changed. The old ordering is now an option
154 by the name of --alphabetical. Adding the option to EMERGE_DEFAULT_OPTS
155 in make.conf will restore the old behaviour permanently.
156 * The deprecated --inject has been removed, use /etc/portage/profile/package.provided
157 * The deprecated --upgradeonly has been removed, use /etc/portage/package.*
159 * 'emerge sync' has been deprecated, use 'emerge --sync' instead (same
161 * Tools that call emerge should override the EMERGE_DEFAULT_OPTS environment
162 variable or use the emerge --ignore-default-opts option.
163 * rsync option handling has been redesigned, instead of RSYNC_* variables
164 use PORTAGE_RSYNC_EXTRA_OPTS from now on.
165 * autouse (use.defaults) has been deprecated by specifying USE_ORDER in make.defaults
166 Users may still turn this back on by specifying USE_ORDER="env:pkg:conf:auto:defaults"
167 in make.conf. Interested in figuring out what use flags were turned off? Check out
168 /usr/portage/profiles/base/use.defaults and other use.defaults files that correspond