summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2008-12-28 22:01:09 +0000
committerZac Medico <zmedico@gentoo.org>2008-12-28 22:01:09 +0000
commit510d819c708486ff582457cf5169543a751d929c (patch)
treeb64b43f5c60dbb5a3c6e0c0d98e361b1c0a08953 /RELEASE-NOTES
parentInside git_sync_timestamps(), use git-diff-index for the same reason that (diff)
downloadportage-idfetch-510d819c708486ff582457cf5169543a751d929c.tar.gz
portage-idfetch-510d819c708486ff582457cf5169543a751d929c.tar.bz2
portage-idfetch-510d819c708486ff582457cf5169543a751d929c.zip
Wrap lines to 80 columns and remove extra blank lines.
svn path=/main/trunk/; revision=12361
Diffstat (limited to 'RELEASE-NOTES')
-rw-r--r--RELEASE-NOTES39
1 files changed, 19 insertions, 20 deletions
diff --git a/RELEASE-NOTES b/RELEASE-NOTES
index 47627acd..d0437c02 100644
--- a/RELEASE-NOTES
+++ b/RELEASE-NOTES
@@ -4,19 +4,20 @@ Features/major bugfixes are listed in NEWS
portage-2.2
==================================
-* Portage now warns if an ebuild repository does not have a name, as several new
- features in 2.2 make use of or require named repositories. The repository name
- is stored in profiles/repo_name in each repository.
-* Package set support: There are several important notes regarding package sets:
- - setnames have to be prefixed with @ (exceptions: 'world' and 'system' can be
- 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
- - 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.
+* Portage now warns if an ebuild repository does not have a name, as several
+ new features in 2.2 make use of or require named repositories. The repository
+ name is stored in profiles/repo_name in each repository.
+* Package set support: There are several important notes regarding package
+ sets:
+ - setnames have to be prefixed with @ (exceptions: 'world' and 'system' can
+ be 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
+ - 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).
+ by the world_sets file).
* "world" does no longer include "system" unconditionally, but you can add
"@system" to the world_sets file to restore the old state.
@@ -26,15 +27,16 @@ portage-2.1.6
* FEATURES=fixpackages is now enabled by default via make.globals. Set
FEATURES="-fixpackages" in make.conf if you'd like to disable it.
* The python namespace for portage has been sanitized, all portage related code
- is now contained within the portage namespace. External script should be updated
- accordingly, though links exist for backward compability.
+ is now contained within the portage namespace. External script should be
+ updated accordingly, though links exist for backward compability.
* -* support in package.keywords was changed as it was inconsistent with
- ACCEPT_KEYWORDS behavior (also see http://dev.gentoo.org/~genone/docs/KEYWORDS.stupid).
- Previously having -* in package.keywords matched packages with KEYWORDS="-*",
+ ACCEPT_KEYWORDS behavior (also see
+ http://dev.gentoo.org/~genone/docs/KEYWORDS.stupid).
+ Previously having -* in package.keywords matched packages with KEYWORDS="-*",
now it resets the ACCEPT_KEYWORDS list for the given atom like it does when
used in ACCEPT_KEYWORDS.
- For packages that don't specify any other KEYWORDS you can use the new ** token
- as documented in portage(5) to disable KEYWORDS filtering completely.
+ For packages that don't specify any other KEYWORDS you can use the new **
+ token as documented in portage(5) to disable KEYWORDS filtering completely.
portage-2.1.5
==================================
@@ -47,7 +49,6 @@ portage-2.1.5
earlier phase (such as pkg_preinst) and store the result in a global
variable to be accessed by pkg_postinst when it is called. Bug #226505
tracks all issues related to this phase execution order change.
-
* 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
@@ -57,13 +58,11 @@ portage-2.1.5
that override eclasses from PORTDIR (in this case, you may have disabled
a relevant warning message by setting PORTAGE_ECLASS_WARNING_ENABLE="0" in
make.conf).
-
* The parallel-fetch feature is now enabled by default. It is optimized
to avoid doing redundant checksums for previously downloaded files that have
the correct size. Run `tail -f /var/log/emerge-fetch.log` in a
terminal to view parallel-fetch progress. Add FEATURES="-parallel-fetch"
to /etc/make.conf if you want to disable this feature.
-
* For extra careful dependency handling, emerge has a new --complete-graph
option that causes it to consider the deep dependencies of all packages from
the system and world sets. With this option enabled, emerge will bail out