From: Zac Medico <zmedico@gentoo.org>
Date: Fri, 14 Sep 2012 18:10:40 +0000 (-0700)
Subject: portage.5: remove {un,}set_unless_changed docs
X-Git-Tag: v2.2.0_alpha129~20
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=0cced1bd17ce277604b47717cc00ae2f13bdc5f6;p=portage.git

portage.5: remove {un,}set_unless_changed docs

These functions were removed in commit
25a5296f29bc7153fa29e2dfe8de9d08d40d9944.
---

diff --git a/man/portage.5 b/man/portage.5
index 49f8dcda0..173e32679 100644
--- a/man/portage.5
+++ b/man/portage.5
@@ -742,19 +742,6 @@ such as \fBFEATURES\fR and \fBINSTALL_MASK\fR will not produce the intended
 results if they are set in bashrc, and therefore
 \fB/etc/portage/package.env\fR should be used instead.
 
-set_unless_changed and unset_unless_changed functions can be used to set or
-unset given variables only if these variable have not been set to values
-different than values set in make.conf. This functionality can be useful for
-temporary overriding of these variables during emerge invocation. Variables
-set without using set_unless_changed will unconditionally override variables
-set during emerge invocation.
-
-.I Syntax:
-.nf
-set_unless_changed VARIABLE=VALUE
-unset_unless_changed VALUE
-.fi
-
 Portage will source all of these bashrc files after \fB/etc/portage/bashrc\fR
 in the following order:
 .nr step 1 1