aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPetteri Räty <betelgeuse@gentoo.org>2007-12-10 21:23:30 +0000
committerPetteri Räty <betelgeuse@gentoo.org>2007-12-10 21:23:30 +0000
commita647177d888efe8e67a9dde000878a716341f9d2 (patch)
tree0d03b7c9b37b4611a1a4c7445c30b4aaa369e82e /general-concepts/use-flags
parentdon't kill png files in icons/ on clean (diff)
downloaddevmanual-a647177d888efe8e67a9dde000878a716341f9d2.tar.gz
devmanual-a647177d888efe8e67a9dde000878a716341f9d2.tar.bz2
devmanual-a647177d888efe8e67a9dde000878a716341f9d2.zip
Add note that pkg_prerm and pkg_postrm use USE flag values saved in VDB. Fixes bug #183070. Remove section claiming that it's not possible to force enable use flags in profiles because that is no longer true after the introduction of package.use.force.
git-svn-id: svn+ssh://svn.gentoo.org/var/svnroot/devmanual/trunk@106 176d3534-300d-0410-8db8-84e73ed771c3
Diffstat (limited to 'general-concepts/use-flags')
-rw-r--r--general-concepts/use-flags/text.xml20
1 files changed, 6 insertions, 14 deletions
diff --git a/general-concepts/use-flags/text.xml b/general-concepts/use-flags/text.xml
index 736d229..0717f6f 100644
--- a/general-concepts/use-flags/text.xml
+++ b/general-concepts/use-flags/text.xml
@@ -20,6 +20,12 @@ No combination of <c>USE</c> flags should cause a package to fail to build.
Packages should not configure and link based upon what is available at compile time
<d/> any autodetection must be overridden.
</p>
+
+<note>
+The status of USE flags is saved in the VDB, and their value in
+<c>pkg_prerm</c> and <c>pkg_postrm</c> is taken from there. This means that setting or
+unsetting a USE flag between merge and unmerge has no effect.
+</note>
</body>
<section>
@@ -92,20 +98,6 @@ Users of non-x86 would see the following when doing <c>emerge -pv vplayer</c>:
To get a flag added to <c>use.mask</c>, ask the relevant arch team.
</p>
-<p>
-So what's the problem with <c>noblah</c> flags? There's no way to forcibly
-<e>enable</e> a given USE flag on a particular profile. So, something like:
-</p>
-
-<codesample lang="ebuild">
-RDEPEND="!noalsa? ( media-libs/alsa )"
-</codesample>
-
-<p>
-... will make your package unusable by archs without ALSA support, and there
-is no way to fix it that doesn't involve adding in nasty <c>arch?</c> flags.
-</p>
-
</body>
</section>