From d2ccca23173dd9dac8a9faa0ace13d9834a2b8c7 Mon Sep 17 00:00:00 2001 From: Warren Block Date: Fri, 4 Apr 2014 02:02:41 +0000 Subject: [PATCH] Whitespace-only fixes, translators please ignore. --- .../porters-handbook/special/chapter.xml | 88 ++++++++++--------- 1 file changed, 45 insertions(+), 43 deletions(-) diff --git a/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml b/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml index fef0f80b88..f703460c37 100644 --- a/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml +++ b/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml @@ -1217,11 +1217,9 @@ USE_XORG= x11 xpm Updating Desktop Database If a port has a MimeType entry in its - portname.desktop, - the desktop database must be updated after install and - deinstall. To do this, define USES= - desktop-file-utils. - + portname.desktop, the desktop database + must be updated after install and deinstall. To do this, + define USES= desktop-file-utils. @@ -1229,10 +1227,9 @@ USE_XORG= x11 xpm DESKTOP_ENTRIES Macro Desktop entries can be easily created for applications - by using the DESKTOP_ENTRIES variable. - A file named - name.desktop - will be created, installed, and added to the + by using the DESKTOP_ENTRIES variable. A + file named name.desktop will be + created, installed, and added to the pkg-plist automatically. Syntax is: @@ -1282,14 +1279,18 @@ USE_XORG= x11 xpm Ports That Require Qt The Ports Collection provides support for Qt 4 and Qt 5 - frameworks with the USE_QTx variable, - where x is 4 or 5. USE_QTx should be - set to the list of required Qt components (libraries, - tools, plugins). The Qt 4 and Qt 5 frameworks are quite similar. - The main difference is the set of supported components. + frameworks with the + USE_QTx + variable, where x is + 4 or 5. + USE_QTx should + be set to the list of required Qt components (libraries, + tools, plugins). The Qt 4 and Qt 5 frameworks are quite + similar. The main difference is the set of supported + components. - The Qt framework exports a number of variables which can be used - by ports, some of them listed below: + The Qt framework exports a number of variables which can + be used by ports, some of them listed below: Variables Provided to Ports That Use Qt @@ -1304,12 +1305,14 @@ USE_XORG= x11 xpm QMAKE - Full path to qmake binary. + Full path to qmake + binary. LRELEASE - Full path to lrelease utility. + Full path to lrelease + utility. @@ -1362,30 +1365,30 @@ PLIST_SUB+= QT_INCDIR=${QT_INCDIR_REL} \ QT_PLUGINDIR=${QT_PLUGINDIR_REL} Some configure scripts do not support the arguments above. - To suppress modification ofCONFIGURE_ENV and - CONFIGURE_ARGS, set the + To suppress modification ofCONFIGURE_ENV + and CONFIGURE_ARGS, set the QT_NONSTANDARD variable. - Component Selection Individual Qt tool and library dependencies must be - specified in the USE_QTx variable. Every - component can be suffixed with + specified in the + USE_QTx + variable. Every component can be suffixed with _build or _run, the - suffix indicating whether the component should be depended - on at buildtime or runtime. If unsuffixed, - the component will be depended on at both build- and - runtime. Usually, library components should be specified - unsuffixed, tool components should be specified with the - _build suffix and plugin components - should be specified with the _run suffix. - The most commonly used components are listed below (all - available components are listed in - _USE_QT_ALL, _USE_QT4_ONLY, - and _USE_QT5_ONLY variables in + suffix indicating whether the component should be depended on + at buildtime or runtime. If unsuffixed, the component will be + depended on at both build- and runtime. Usually, library + components should be specified unsuffixed, tool components + should be specified with the _build suffix + and plugin components should be specified with the + _run suffix. The most commonly used + components are listed below (all available components are + listed in _USE_QT_ALL, + _USE_QT4_ONLY, and + _USE_QT5_ONLY variables in /usr/ports/Mk/bsd.qt.mk):
@@ -1587,7 +1590,7 @@ PLIST_SUB+= QT_INCDIR=${QT_INCDIR_REL} \ builds, which can be enabled by specifying the outsource argument (see USES= qmake - example). + example).
Variables for Ports That Use @@ -1636,13 +1639,11 @@ PLIST_SUB+= QT_INCDIR=${QT_INCDIR_REL} \ <application>qmake</application> for a Qt 4 port:</para> <programlisting>USES= qmake:outsource -USE_QT4= moc_build -</programlisting> +USE_QT4= moc_build</programlisting> <para>For a Qt 5 port:</para> <programlisting>USES= qmake:outsource -USE_QT5= buildtools_build -</programlisting> +USE_QT5= buildtools_build</programlisting> </example> <para>Qt applications are often written to be cross-platform @@ -1729,7 +1730,8 @@ USE_QT5= buildtools_build <row> <entry><literal>automoc4</literal></entry> - <entry>Build tool to automatically generate moc files</entry> + <entry>Build tool to automatically generate moc + files</entry> </row> <row> @@ -1739,7 +1741,8 @@ USE_QT5= buildtools_build <row> <entry><literal>soprano</literal></entry> - <entry>Library for Resource Description Framework (RDF)</entry> + <entry>Library for Resource Description Framework + (RDF)</entry> </row> <row> @@ -1847,8 +1850,7 @@ USE_QT5= buildtools_build environment variable and/or <command>make</command> arguments. Currently <varname>KDE4_PREFIX</varname> is identical to the default <varname>PREFIX</varname>, - <literal>${LOCALBASE}</literal>. - </para> + <literal>${LOCALBASE}</literal>.</para> <example xml:id="kde4-components-example"> <title><varname>USE_KDE4</varname> Example