From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C64EF138B0F for ; Tue, 19 Feb 2013 15:16:48 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 486E221C014; Tue, 19 Feb 2013 15:16:48 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D8D6621C014 for ; Tue, 19 Feb 2013 15:16:47 +0000 (UTC) Received: from hornbill.gentoo.org (hornbill.gentoo.org [94.100.119.163]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id C87C533DE6B for ; Tue, 19 Feb 2013 15:16:46 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by hornbill.gentoo.org (Postfix) with ESMTP id 5EC04E4073 for ; Tue, 19 Feb 2013 15:16:45 +0000 (UTC) From: "Sven Eden" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Sven Eden" Message-ID: <1361287058.d15c370abf49b4267f9ce51c7a011413e6235e61.yamakuzure@gentoo> Subject: [gentoo-commits] proj/ufed:master commit in: / X-VCS-Repository: proj/ufed X-VCS-Files: ufed.8.in X-VCS-Directories: / X-VCS-Committer: yamakuzure X-VCS-Committer-Name: Sven Eden X-VCS-Revision: d15c370abf49b4267f9ce51c7a011413e6235e61 X-VCS-Branch: master Date: Tue, 19 Feb 2013 15:16:45 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org X-Archives-Salt: 238aad85-b61b-4b58-abe2-97e9bb57cb4a X-Archives-Hash: efc95d986b5a0e445604892051b3db3a commit: d15c370abf49b4267f9ce51c7a011413e6235e61 Author: Sven Eden gmx de> AuthorDate: Tue Feb 19 15:17:38 2013 +0000 Commit: Sven Eden gmx de> CommitDate: Tue Feb 19 15:17:38 2013 +0000 URL: http://git.overlays.gentoo.org/gitweb/?p=proj/ufed.git;a=commit;h=d15c370a Fixed local/global section in the man page. --- ufed.8.in | 33 ++++++++++++++++----------------- 1 files changed, 16 insertions(+), 17 deletions(-) diff --git a/ufed.8.in b/ufed.8.in index 652f973..523cbf4 100644 --- a/ufed.8.in +++ b/ufed.8.in @@ -48,23 +48,22 @@ in @GENTOO_PORTAGE_EPREFIX@/usr/portage/profiles/use.local.desc. .B What are "global" and "local" USE flags? -From the perspective of any package there is no distinction between "local" and -"global" flags. A package either listens to a specific flag or it doesn't. - -The difference is the description, and maybe the impact of whether a flag is -set or not. If a package supports a flag that has a global description in -@GENTOO_PORTAGE_EPREFIX@/usr/portage/profiles/use.desc but does make use of -the flag differently, then the package maintainer has to add a local -description to the packages metadata.xml file. -.br -The same applies to flags that have no global description, a local one must be -provided then. - -An example would be a package with the USE flag "tiff", that does not only add -support for the TIFF image format, but changes the output format of the -program installed. The USE flag then would have a different impact on the -package than described in the global description; a local description must be -provided then. +Global USE flags are called such because they represent functionality that is +found in a wider variety of packages. For example, the global flag "cjk" is +about adding / not adding support for Eastern-Asian languages, which affects +a multitude of various packages. Global flags are described in +@GENTOO_PORTAGE_EPREFIX@/usr/portage/profiles/use.desc. + +Local USE flags are unique package-wise, because the functionality they stand +for is only found in that particular package and no other. See +@GENTOO_PORTAGE_EPREFIX@/usr/portage/profiles/use.local.desc for a full, +per-package listing of all local USE flags. + +It still happens that a flag which is defined as global is also defined as +local for one or more packages. That is because the general definition of the +global flag takes on specialized semantics in some particular package. It also +occurs that multiple packages define a local flag of the same name - the +meaning of the flag differs, however, for each package. .B What are "Masked" and "Forced" flags?