Bug 748197

Summary:	Ability to add arbitrary content to publican.cfg through Content Spec
Product:	[Community] PressGang CCMS	Reporter:	Joshua Wulf <jwulf>
Component:	CSProcessor	Assignee:	Ali Abbas <alabbas>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.x	CC:	jwulf, lcarlon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	0.0.10	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-04 07:18:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Joshua Wulf 2011-10-22 23:42:39 UTC

(Let's start with publican.cfg, and see if you can design it in such a way that it can be extended to other files later)

In the header of the Content Spec, enable this:

ID=1
Title = Zanata Quickstart Guide
Product = Zanata
Version = 1.4
DTD = Docbook 4.5
publican.cfg = [cvs_branch: DOCS-RHEL-6
cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist
cvs_pkg: Zanata-Zanata_Quickstart_Guide-1-web-__LANG__]
[Technology: Zanata]

In this case, all of the content between the square brackets will be added to the end of the publican.cfg file when the book is built by the CSBuilder.

The only checking that is done by the CSProcessor is to make sure that:

publican.cfg is there, and that there is a [] delimited block following it.

Comment 1 Ali Abbas 2011-11-04 05:57:13 UTC

This has been implemented in Build 10. This is used by adding the publican.cfg = then followed by the content within square brackets as described above. If square brackets need to be used inside the content, they have to be escaped with the escaped character (\).