os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Clean up some grammar [1] and spacing [2]

Browse source 
- Document KDE 3/4 conflicts [1]

Reviewed by:	keramida [1] trhodes [2]
Approved by:	trhodes
This commit is contained in:
Thomas Abthorpe 2009-10-04 05:49:07 +00:00
parent 2e53c09697
commit 01bb24bbc0
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=34758
1 changed files with 13 additions and 3 deletions

16
en_US.ISO8859-1/books/porters-handbook/book.sgml
View file

@ -5885,11 +5885,21 @@ do-configure:
<para>KDE 4.x ports are installed into <literal>&dollar;{KDE4_PREFIX}</literal>,
which is <filename>/usr/local/kde4</filename> currently, to avoid conflicts
with KDE 3.x ports. This is achieved by specifying <literal>kdeprefix</literal>
component, which overrides default <makevar>PREFIX</makevar>. The ports however
respect <makevar>PREFIX</makevar> set via <envar>MAKEFLAGS</envar> environment
with KDE 3.x ports. This is achieved by specifying the <literal>kdeprefix</literal>
component, which overrides the default <makevar>PREFIX</makevar>. The ports however
respect any <makevar>PREFIX</makevar> set via <envar>MAKEFLAGS</envar> environment
variable and/or <application>make</application> arguments.</para>
<para>KDE 4.x ports may conflict with KDE 3.x ports, so when the
<literal>kdeprefix</literal> component is enabled, they are installed in
<literal>&dollar;{KDE4_PREFIX}</literal>. The default value of
<literal>KDE4_PREFIX</literal> is currently
<filename>/usr/local/kde4</literal>. Installing the KDE 4.x ports into
a custom <literal>PREFIX</literal> is also possible. When
<literal>PREFIX</literal> is set via the <envar>MAKEFLAGS</envar>
environment variable or via <application>make</application> options it
overrides the value configured by <literal>kdeprefix</literal>.</para>
<example id="kde4-components-example">
<title><makevar>USE_KDE4</makevar> example</title>