Use the package name's entity where relevant

This commit is contained in:
Pierre Pronchery 2015-01-13 23:27:15 +01:00
parent 446f56b846
commit 2619f6c455

View File

@ -160,15 +160,15 @@
<title>Script targets</title> <title>Script targets</title>
<para> <para>
Scripts have to be provided by the software project itself, as Scripts have to be provided by the software project itself, as
configure does not provide any pre-installed set of standard &package; does not provide any pre-installed set of standard
scripts. A few sample scripts are, however, distributed along with scripts. A few sample scripts are, however, distributed along with
the source code of the configure project, and introduced here. the source code of the &package; project, and introduced here.
</para> </para>
<para> <para>
These scripts are primarily meant to allow further integration of These scripts are primarily meant to allow further integration of
the build process, as defined by the Makefiles generated, with the the build process, as defined by the Makefiles generated, with the
requirements of a software project beyond that of compiling code. requirements of a software project beyond that of compiling code.
configure is already known to have been successfully integrated this &package; is already known to have been successfully integrated this
way with: way with:
<itemizedlist> <itemizedlist>
<listitem><para>AppBroker: integration with the DeforaOS distributed <listitem><para>AppBroker: integration with the DeforaOS distributed
@ -195,7 +195,7 @@
<refsect3> <refsect3>
<title>Writing scripts</title> <title>Writing scripts</title>
<para> <para>
It is naturally possible to write scripts for integration with configure. It is naturally possible to write scripts for integration with &package;.
<!-- FIXME complete this section --> <!-- FIXME complete this section -->
</para> </para>
</refsect3> </refsect3>