Skynet currently generates a specfile with a %post statement that looks like this: %post -n %{doc_product}-%{doc_books}-%{doc_version}-web-%{doc_lang} %{__perl} -e 'foreach my $book (@books) { system(q|publican update_db --add --lang="%{doc_lang}" --formats="html" --product="%{doc_product}" --version="%{doc_version}" --name="$book" --subtitle="%{doc_product} %{doc_version} documentation" --abstract="Unported %{doc_product} %{doc_version} HTML documentation."|);}' When we build a book with this, the book stages fine but is not added to the Publican TOC. Rudi hand-wrote a %post that works properly, but I'm unsure the best way to get it integrated into the build process without breaking every other product which needs to build: %post -n JBoss_Enterprise_Application_Platform-Beta_Documentation-6-web-en-US publican update_db --add --lang="en-US" --formats="html" --name="Beta_Documentation" --version="6" --product="JBoss_Enterprise_Application_Platform" --subtitle="Consolidated documentation suite for JBoss Enterprise Application Platform 6 Beta" --abstract="This Beta Documentation release consolidates all available documentation for the JBoss Enterprise Application Platform 6 Beta into a single canonical document." In fact, Rudi's script fixes (by brute force) a lot of potential build problems. We need to look at what his script is doing and do it within Skynet itself, based on per-product properties (I think).
Rudi, can you please attach the latest iteration of your script?
Created attachment 577608 [details] Script for post processing
This is fragile, contains many assumptions, and is potentially dangerous. Please regard as highly suspect.
I'll update the brand to include a tree view generated from the standard Docbook TOC. This way the book scan just be regular publican projects, and we can avoid custom build scripts.
The new version of the builder has been live for a couple of weeks now and no longer uses the custom scripts as described by Matt above. As such I'm gonna close this bug as it's no longer relevant.