From: Marius Mauch Date: Fri, 26 Oct 2007 01:13:26 +0000 (-0000) Subject: update notes about package sets X-Git-Tag: v2.2_pre1~506 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=2b123f4eb00f310eb6e5af3cd6fc8f69755e3c73;p=portage.git update notes about package sets svn path=/main/trunk/; revision=8304 --- diff --git a/RELEASE-NOTES b/RELEASE-NOTES index 076bb12c5..8c1f6b3eb 100644 --- a/RELEASE-NOTES +++ b/RELEASE-NOTES @@ -18,15 +18,15 @@ portage-2.2 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 + - 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 - 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 - - sets can not contain other sets + already installed and added to the worldfile, or in the case of --unmerge all + atoms in a set will be unmerged even if they are depended upon by other + packages portage-2.1.3 ==================================