From 5fc602b34679d888851c9aeb4562d4d8ec8acdaa Mon Sep 17 00:00:00 2001 From: Jeremy Olexa Date: Tue, 13 Jul 2010 16:46:55 -0500 Subject: use-flags: Remove ambiguous 'thing' description. Instead refer to 'thing' as a flag. Reformat source for readability --- general-concepts/use-flags/text.xml | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) (limited to 'general-concepts/use-flags') diff --git a/general-concepts/use-flags/text.xml b/general-concepts/use-flags/text.xml index bc9d165..20ab4ae 100644 --- a/general-concepts/use-flags/text.xml +++ b/general-concepts/use-flags/text.xml @@ -114,25 +114,28 @@ RDEPEND="fakemedia? ( >=media-libs/fakemedia-1-1 )"

-USE flags are categorised as either local or global. A global USE flag must satisfy several criteria: + USE flags are categorised as either local or global. A global USE flag must + satisfy several criteria:

It is used by many different packages.
It is used by many different packages, at least 5 seems to be agreed + upon.
It has a general non-specific purpose.

-The second point is important. If the effect of the thing USE flag upon -pkg-one is substantially different from the effect it has upon pkg-two, -then thing is not a suitable candidate for being made a global flag. In -particular, note that if client and server USE flags are ever -introduced, they can not be global USE flags for this reason. + The second point is important. If the effect of the USE flag upon + pkg-one is substantially different from the effect it has upon + pkg-two, then the flag is not a suitable candidate for being made a + global flag. In particular, note that if client and server + USE flags are ever introduced, they can not be global USE flags for this + reason.

-Before introducing a new global USE flag, it must be discussed on the gentoo-dev -mailing list. + Before introducing a new global USE flag, it must be discussed on the + gentoo-dev mailing list.

-- cgit v1.2.3-65-gdbad