[publican-list] [Bug 677869] New: publican package does not work with conditional book_info.xml

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: publican package does not work with conditional book_info.xml

https://bugzilla.redhat.com/show_bug.cgi?id=677869

           Summary: publican package does not work with conditional
                    book_info.xml
           Product: Publican
           Version: future
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: unspecified
          Priority: unspecified
         Component: publican
        AssignedTo: jfearn at redhat.com
        ReportedBy: lbailey at redhat.com
         QAContact: rlandman at redhat.com
                CC: mmcallis at redhat.com, publican-list at redhat.com
    Classification: Other


Description of problem:
I have two products to document, which are so similar that I decided to use
conditional tags and one source document instead of making two books. To do so,
I made separate Book_Info.xml files - Book_Info_A.xml and Book_Info_B.xml.

Publican builds these books just fine for either product, but the "publican
package" command complains of a lack of Book_Info.xml.

Is it possible to get the package command to check for the <bookinfo> element
instead of the Book_Info.xml file?

---

Workarounds Attempted:

First, I tried adding <phrase condition="a">A</phrase><phrase
condition="b">B</phrase> to the subtitle, productname, etc. tags.
This results in an incorrect packagename:
JBoss_Enterprise_ApplicationWeb_Platform-6.0.0_Release_Notes-6-web-en-US-6.0.0-1.el5
instead of
JBoss_Enterprise_Application_Platform-6.0.0_Release_Notes-6-web-en-US-6.0.0-1.el5
or JBoss_Enterprise_Web_Platform-6.0.0_Release_Notes-6-web-en-US-6.0.0-1.el5
depending on the condition set in publican.cfg.

Next I tried adding the condition to the productname tag, but in this case
publican package just grabs the content of whichever <productname> comes first
in the file, regardless of the condition that is set. Of the two workarounds, I
think this one makes the most sense, if we absolutely must use Book_Info.xml as
the container for the <bookinfo> element.

---

Version-Release number of selected component (if applicable):
publican-2.5-1.fc13.noarch

---

How reproducible:
Every time.

---

Steps to Reproduce:
Try to brew a book whose <productname> is conditional.
Examples here:
https://svn.devel.redhat.com/repos/ecs/JBoss_Enterprise_Application_Platform/trunk/6/

---

Actual results:
Incorrect packagename.

---

Expected results:
Correct packagename.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.