1 News (mainly features/major bug fixes)
6 * Add link level dependency awareness to emerge --depclean and --prune actions
7 in order to protect against uninstallation of required libraries.
8 * Add support for generic package sets (also see RELEASE-NOTES)
9 * Add support for FEATURES=preserve-libs which preserves libraries when the
10 sonames change during upgrade or downgrade, and the @preserved-rebuild
11 package set which rebuilds consumers of preserved libraries.
15 * Improve handling of repositories/overlays for cases in which the same ebuild
16 is provided by multiple repositories but with different masking status, and
17 support for repository constraints on atoms (atom::repo) in configuration
19 * Add emerge --rebuild-if-* options that trigger rebuilds of reverse
20 dependencies when packages are rebuilt or updated. Related --rebuild-exclude
21 and --rebuild-ignore options can be used to avoid rebuilds for specific
23 * Add emerge --reinstall-atoms, --useoldpkg-atoms, and --usepkg-exclude options
24 which can be used to alter selection rules for specific packages.
25 * Add FEATURES=parallel-install and ebuild-locks, allowing for greater
26 parallelization when installing packages (by using finer-grained locks).
31 * Add support for EAPI 4. Refer to the PMS EAPI Cheat Sheet, portage's html
32 docs installed with USE=doc, or `man 5 ebuild` for more info about EAPI 4.
33 Bug #273620 tracks EAPI 4 implementation in portage.
38 * There is a new ipc (inter-process communication) USE flag which is enabled
39 by default. This allows portage to communicate with running ebuild processes,
40 for things like best_version, has_version, and die calls in nested processes.
41 This flag should remain enabled unless it is found to be incompatible with a
42 specific profile or environment. When enabled, it fixes bug #278895,
43 bug #315615, and makes subshell die support more robust (so that repoman's
44 ebuild.nesteddie check is irrelevant).
48 * The top-level __init__.py for the portage python package has been split into
49 many smaller python modules, making the code easier to navigate and allowing
50 small parts of the portage api to be imported with less overhead.
55 * Add license visibility filtering (GLEP 23)
56 * Add --accept-properties option for emerge which allows you to use
57 --accept-properties=-interactive in order to temporarily exclude
59 * Add support for Python 3.0. At least Python 2.6 is now required in order to
60 support the new syntax which is used by Python 3.0.
65 * Add support for a new EAPI="2" value. For more information about new EAPI
66 features, refer to the "Ebuild" chapter of the html documentation that is
67 installed with portage.
68 * Add PORTAGE_IONICE_COMMAND setting for make.conf which is called to adjust
69 IO priority on portage and it's subprocesses.
70 * Add emerge --jobs and --load-average options which specify behavior
71 for building packages in parallel or for generating metadata in parallel
73 * Add emerge --keep-going option to continue as much as possible after
74 an error. When an error occurs, dependencies are recalculated for
75 remaining packages and any with unsatisfied dependencies are
76 automatically dropped. The --skipfirst option automatically drops
77 packages in the same way, and also drops any masked packages.
78 * Add git and subversion support for repoman.
79 * It is now possible to use `emerge <file>` to reinstall the package that
80 installed a particular file. Package contents entries are indexed to
81 improve performance. A command such as `emerge /lib/modules` can serve
82 as a decent substitute for module-rebuild.
83 * Namespace sanitizing: move all portage related code into portage.* namespace,
84 rename portage_foo modules to portage.foo (but keep symlinks for compability)
85 * Add support for news items (GLEP 42)
86 * Add FEATURES=protect-owned which is identical to the collision-protect
87 feature except that files may be overwritten if they are not explicitly
88 listed in the contents of a currently installed package.
93 * For extra careful dependency handling, emerge has a new --complete-graph
94 option that causes it to consider the deep dependencies of all packages from
95 the system and world sets. With this option enabled, emerge will bail out
96 if it determines that the given operation will break any dependencies of
97 the packages that have been added to the graph. Unlike the --deep option,
98 the --complete-graph option does not cause any more packages to be updated
99 than would have otherwise been updated with the option disabled.
100 * Blockers are now resolved automatically in many more cases
101 than before. When it's safe, blocked packages are uninstalled
102 automatically so that users are no longer inconvenienced with the
103 task. Automatically uninstalled packages are displayed in the merge
104 list, marked "uninstall" and highlighted in red. With the --tree
105 option enabled, it's possible to see which package(s) caused other
106 ones to be automatically uninstalled.
107 * The dependency resolver now has a feedback mechanism that helps make atom
108 selections more consistent with previous selections that have been added to
109 the graph. This solves some common cases of bug #1343.
114 * After the initial setup phase, the original ebuild and eclasses are no
115 longer needed because the same ebuild environment is reused for the
116 entire lifecycle of the package, including uninstallation.
117 * The emerge --search action supports searching of both installed and binary packages
118 The --usepkg and --usepkgonly options control which repositories are searched.
123 * Allow per-module setting of PORTAGE_ELOG_CLASSES
124 * Add new elog module "echo" to simply display messages when emerge exits
125 * Add ** as new token for package.keywords to bypass the keyword visibility layer
126 * USE_EXPAND variables such as LINGUAS support a * wildcard that will enable
127 all of the corresponding flags that are listed in IUSE for a given package.
128 USE_EXPAND wildcards such as linguas_* are supported in USE and package.use.
129 * The merge process preserves the modification timestamp of files that it
130 installs. The unmerge process will not uninstall files that are claimed by
131 another package in the same slot.
132 * PDEPEND is now installed as soon as possible so that it behaves more like
133 RDEPEND. This makes PDEPEND more useful for breaking the dependency cycles
134 that are sometimes triggered by RDEPEND and DEPEND.
135 * Enable "echo" and "save_summary" elog modules by default
136 * Fix -* handling in package.keywords to work as intended (reset the accepted
137 keywords list), also see RELEASE-NOTES.
138 * Make elog functionality available to python code
143 * Ebuilds support default USE flags via +flag in IUSE.
144 * New-style virtuals are now usable for packages that depend on themselves for
146 * Profiles support multiple inheritance and package.use.
147 * CONFIG_PROTECT and CONFIG_PROTECT_MASK both support files (not just
149 * Collision protection handles symlinks properly.
150 * Dependencies can be satisfied by installed packages that do not have matching
151 ebuilds in the portage tree or overlay.
152 * Emerge automatically ignores blockers that are made irrelevant by an upgrade.
153 * Emerge supports "reverse blocker detection" which means that the blockers of
154 installed packages will always be respected.
155 * Emerge builds a complete dependency graph in order to ensure correct merge
156 order and detection of circular dependencies.
157 * The world and system sets allow automatic update of all installed slots.
158 * DEPEND atoms support SLOT dependencies of the form ${CATEGORY}/${PN}:${SLOT}.
159 * Development: Extend PYTHONPATH support to allow overriding the hardcoded
160 /usr/lib/portage/pym for development/testing purposes
161 * New "finalize" hook for elog modules enabling modules to perform actions on
162 shutdown (like dispatching collected messages).
163 * New elog modules mail_summary and save_summary that act like the mail/save
164 modules except that they merge messages from multiple packages in a single
166 * New QA loglevel and matching eqawarn function
167 * `ebuild foo test` now always runs src_test if available
168 * If DOC_SYMLINK_DIR is set portage installs symlinks to html documention there
169 * FEATURES="test" automatically implies USE="test".
174 * Profiles support use.force, package.use.force, and package.use.mask files.
176 portage-2.1 (ongoing via pre releases)
179 * FEATURES="confcache" integration; global caching to speed up configure calls,
180 requires dev-util/confcache
181 * elog framework and accompanying modules for logging ebuild warnings, errors
182 and general notices. Collects eerror/ewarn/elog/einfo messages.
183 * New elog function (should replace einfo in many cases)
184 * version syntax enhancements allowing multiple suffixes and a new 'cvs'
185 version prefix for denoting "live sources" ebuilds.
186 * config files as directories enabling more flexible settings management.
187 * Addition of an register_die_hook method that allows ebuild/eclasses to
188 register functions to be called for better debugging on errors.
189 * Addition of pre and post user hookable functions for each ebuild phase, accessible
190 via portage bashrc. Example would be pre_src_unpack .
191 * cache refactoring- runtime improvement from 35% -> 65%.
192 * Intelligently handle and display USE_EXPAND-based IUSE variables.
193 * FEATURES="parallel-fetch". Download in parallel to compilation.
194 * Include a "changed or new" USE flag output when --verbose isn't specified.
195 * Support for splitting out debug information into separate files in
197 * exec subsystem refactoring (now with less bugs!)
198 * Added sha256 and rmd160 hashes for digests/manifests
199 * Make --emptytree only apply to ${ROOT} rather than always including /.
200 * Allow packages to be upgraded that are only depended on via a
201 "|| ( =cat/pkg-1* =cat/pkg-2* )" construct.
202 * Ebuild output is no longer cut off early when using PORT_LOGDIR.
203 * Distfiles indirection- $DISTFILES access goes through a tmp dir to fail
204 access to files not listed in SRC_URI.
205 * Emerge now uses --resume to restart itself after portage upgrade.
206 * Atomic file updates via the new atomic_ofstream class.
207 * Global updates and fixpackages performance optimizations.
208 * Tests show that file locking is now more reliable.
209 * A bash call stack is printed when an ebuild dies in ebuild.sh.
210 * New rsync option handling by using a generic PORTAGE_RSYNC_EXTRA_OPTS variable
211 * Manifest2 support that will allow digest-* files to be eliminated from the tree.