From 2619f6c455774d6ce6d1a3168f79c2a9ea92e0f1 Mon Sep 17 00:00:00 2001 From: Pierre Pronchery Date: Tue, 13 Jan 2015 23:27:15 +0100 Subject: [PATCH] Use the package name's entity where relevant --- doc/project.conf.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/project.conf.xml b/doc/project.conf.xml index 379813f..7e3d5c0 100644 --- a/doc/project.conf.xml +++ b/doc/project.conf.xml @@ -160,15 +160,15 @@ Script targets 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 - the source code of the configure project, and introduced here. + the source code of the &package; project, and introduced here. These scripts are primarily meant to allow further integration of the build process, as defined by the Makefiles generated, with the 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: AppBroker: integration with the DeforaOS distributed @@ -195,7 +195,7 @@ Writing scripts - It is naturally possible to write scripts for integration with configure. + It is naturally possible to write scripts for integration with &package;.