portage-2.2
-------------
+* It is now possible to use `emerge <file>` to reinstall the package that
+ installed a particular file. Package contents entries are indexed to
+ improve performance. A command such as `emerge /lib/modules` can serve
+ as a decent substitute for module-rebuild.
* Namespace sanitizing: move all portage related code into portage.* namespace,
rename portage_foo modules to portage.foo (but keep symlinks for compability)
* Add license visibility filtering (GLEP 23)
-* Enable "echo" and "save_summary" elog modules by default
-* Fix -* handling in package.keywords to work as intended (reset the accepted
- keywords list), also see RELEASE-NOTES.
* Experimental support for preserving old library files on package upgrades
based on FEATURES=preserve-libs
-* Make elog functionality available to python code
* Add support for news items (GLEP 42)
* Add support for generic package sets (also see RELEASE-NOTES)
portage-2.1.5
-==================================
+-------------
+* Blockers are now resolved automatically in many more cases
+ than before. When it's safe, blocked packages are uninstalled
+ automatically so that users are no longer inconvenienced with the
+ task. Automatically uninstalled packages are displayed in the merge
+ list, marked "uninstall" and highlighted in red. With the --tree
+ option enabled, it's possible to see which package(s) caused other
+ ones to be automatically uninstalled.
* The dependency resolver now has a feedback mechanism that helps make atom
selections more consistent with previous selections that have been added to
the graph. This solves some common cases of bug #1343.
* After the initial setup phase, the original ebuild and eclasses are no
longer needed because the same ebuild environment is reused for the
entire lifecycle of the package, including uninstallation.
+* The emerge --search action supports searching of both installed and binary packages
+ The --usepkg and --usepkgonly options control which repositories are searched.
portage-2.1.3
-------------
* PDEPEND is now installed as soon as possible so that it behaves more like
RDEPEND. This makes PDEPEND more useful for breaking the dependency cycles
that are sometimes triggered by RDEPEND and DEPEND.
+* Enable "echo" and "save_summary" elog modules by default
+* Fix -* handling in package.keywords to work as intended (reset the accepted
+ keywords list), also see RELEASE-NOTES.
+* Make elog functionality available to python code
portage-2.1.2
-------------
used without the prefix)
- they may currently only include simple and versioned atoms or other sets, use
conditionals or any-of constructs aren't possible yet
- - emerge makes no difference atm whether you pass a setname or all atoms contained
- in the set to it, this means that without options packages will be remerged if
- already installed, or in the case of --unmerge all atoms in a set will be
- unmerged even if they are depended upon by other packages. This may change in
- future versions.
- sets can be referenced either in other file-based sets or as argument to emerge, but
not in ebuilds, config files or other tools at this time.
+ - packages won't be unmerged if they are referenced by an installed package
+ set (with the exception of the world set, and installed being determined
+ by the world_sets file).
* "world" does no longer include "system" unconditionally, but you can add
- "@system" to the worldfile to restore the old state.
+ "@system" to the world_sets file to restore the old state.
portage-2.1.5
==================================
-* It is now possible to use `emerge <file>` to reinstall the package that
- installed a particular file. Package contents entries are indexed to
- improve performance. A command such as `emerge /lib/modules` can serve
- as a decent substitute for module-rebuild.
-
* The pkg_postinst phase is now called after the previous version of a
package has been removed. As a consequence, it is no longer possible
to call has_version in pkg_postinst to detect whether the current
variable to be accessed by pkg_postinst when it is called. Bug #226505
tracks all issues related to this phase execution order change.
-* Blockers are now resolved automatically in many more cases
- than before. When it's safe, blocked packages are uninstalled
- automatically so that users are no longer inconvenienced with the
- task. Automatically uninstalled packages are displayed in the merge
- list, marked "uninstall" and highlighted in red. With the --tree
- option enabled, it's possible to see which package(s) caused other
- ones to be automatically uninstalled.
-
* The metadata-transfer feature is now disabled by default. This disables the
"Updating Portage cache" routine that used to run at the tail end of each
`emerge --sync` operation. If you use something like the sqlite module and
* There is no need to have a complete portage tree available when installing binary
packages or uninstalling packages, but a warning message will still be displayed if
it appears that a valid profile is not available.
-* The emerge --search action supports searching of both installed and binary packages
- The --usepkg and --usepkgonly options control which repositories are searched.
portage-2.1.3
==================================
local messagetype
[ -z "${1}" -o -z "${T}" -o ! -d "${T}/logging" ] && return 1
case "${1}" in
- INFO|WARN|ERROR|LOG|QA)
+ BLANK|INFO|WARN|ERROR|LOG|QA)
messagetype="${1}"
shift
;;
return 0
}
+eblank() {
+ [[ ${LAST_E_CMD} == "eblank" ]] && return 0
+ elog_base BLANK
+ [[ ${RC_ENDCOL} != "yes" && ${LAST_E_CMD} == "ebegin" ]] && echo
+ echo -e " ${BLANK}*${NORMAL}"
+ LAST_E_CMD="eblank"
+ return 0
+}
+
eqawarn() {
elog_base QA "$*"
[[ ${RC_ENDCOL} != "yes" && ${LAST_E_CMD} == "ebegin" ]] && echo
PORTAGE_WORKDIR_MODE="0700"
# Some defaults for elog
-PORTAGE_ELOG_CLASSES="log warn error"
+PORTAGE_ELOG_CLASSES="blank log warn error"
PORTAGE_ELOG_SYSTEM="save_summary echo"
PORTAGE_ELOG_MAILURI="root"
projects / portage.git / commitdiff