From: Marius Mauch Date: Sun, 21 Oct 2007 10:55:14 +0000 (-0000) Subject: add some notes about restrictions wrt package sets X-Git-Tag: v2.2_pre1~568 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=61cdd341bb21b62af6f3b29bf162af68cfec81be;p=portage.git add some notes about restrictions wrt package sets svn path=/main/trunk/; revision=8206 --- diff --git a/NEWS b/NEWS index 7d87209e5..13c0b8474 100644 --- a/NEWS +++ b/NEWS @@ -13,6 +13,7 @@ portage-2.2 based on FEATURES=preserve-libs, USE AT YOUR OWN RISK!!! * 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.3 ------------- diff --git a/RELEASE-NOTES b/RELEASE-NOTES index 12cca880d..1c3e3aeab 100644 --- a/RELEASE-NOTES +++ b/RELEASE-NOTES @@ -17,6 +17,16 @@ 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: + - they may currently only include simple and versioned atom, use conditionals + or any-of constructs aren't possible yet + - emerge makes no difference atm wether 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 and added to the worldfile (exception: "world" and "system" + are still handled specially), or in the case of --unmerge all atoms in a set + will be unmerged even if they are depended upon by other packages + - sets shadow packages with the same name + portage-2.1.3 ==================================