Re: [docbook-apps] Best way to structure a source code tree

Sounds like you could just keep everything in one directory where you check your files out from CVS.  I keep my source files in CVS also but keep them in subject related directories like: HAclusters, workstations, LDAP, SSH, usermaint etc ...
  
 
  
In keep these directories in $HOME/MYNOTES and I have a Makefile in each
  
of these directories so I do things like ...
  
 
  
$ cd
  
$ cd MYNOTES
  
$ make pdfs
  
 
  
... to generate all of my source into PDF docs.  Or ...
  
 
  
$ cd MYNOTES
  
$ make
  
$ make install
  
 
  
... which generates all my source xml into PDF, html, chunk, text, and rtf
  
and have all on that put on to my web server (make install).
  
 
  
You should look into make it is a great tool.

Mike Broschinsky
 <> wrote:
  While not directly related to any docbook app, this is a question I'm struggling with as a beginner: how do I structure the source code tree for my article/book/etc.?

For example, we publish a manual with five chapters, eight appendices, and a sprinkling of images.

Is there a best practice for structuring the source? I mean, I could just mirror the way that TDG is structured, but I would really like to understand *why* it's structured that way. And also to understand why there are subtle differences between the structure of the current TDG and TDG5:

http://cvs.sourceforge.net/viewcvs.py/docbook/defguide/
http://cvs.sourceforge.net/viewcvs.py/docbook/defguide5/

Does my question make any sense at all? Any pointers would be *greatly*
 appreciated.

Thanks,

Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: 
For additional commands, e-mail: 

		 Yahoo! Mail
 
Use Photomail to share photos without annoying attachments.