> > > -----Original Message----- > From: David Nalley [mailto:da...@gnsa.us] > Sent: Wednesday, August 08, 2012 6:12 AM > To: cloudstack-dev@incubator.apache.org > Subject: Re: DOCS: problems with using entities > > On Wed, Aug 8, 2012 at 2:40 AM, Radhika Puthiyetath < > radhika.puthiyet...@citrix.com> wrote: > > Hi David, > > > > Here is the readme file that Jessica created for generating various book > set from the XML files. > > > > The readme has the complete information on generating different book > sets by appropriately declaring in the .cfg file. > > > > Regards > > -Radhika > > I understand what the intent is, it's just failing now that we have added > entities to the mix. > > Ewan: The build now works in jenkins. Sadly, symlinks don't, for whatever > reason. (work fine on my local machine, but not on jenkins > itself) I had to instantiate a real file for it to build. > > --David >
For release 4.0, I am not sure we need to create separate "books". It should be sufficient to generate the entire docs directory using publican-all.cfg. Then we will have one document that contains "chapters" on installation, administration, developer's info, and so on. I had just started to work on setting up the repo for automated builds of multiple books. You can see some of my first attempts in the configs subdirectory under docs, where I was saving my working files during testing (before David kindly moved the docs files over to the Apache repo). I should probably delete that directory now. I have just added six new publican.cfg files named for the "books" they create: publican-install.cfg, publican-devguide.cfg, etc. I am not sure whether this can be done to create Book_Info_Install, cloudstack-install.ent, and so on for each "book." I haven't tested it. Publican does offer a couple of techniques for generating what they call "book sets," but I don't think either technique will work. Option #1 works only with svn, so that isn't a fit for us. Option #2 seems to assume that the content of the books doesn't overlap, and that is definitely not a fit for us. We need to come up with something clever. I'm glad to see more attention focusing on this task. Please keep sending ideas! Jessica T. CloudStack Tech Pubs
