nALFS Users Guide Update

James Robertson jwrober at linuxfromscratch.org
Tue Sep 30 07:35:14 PDT 2003


Neven Has wrote:
> On Mon, Sep 29, 2003 at 09:52:29PM -0500, James Robertson wrote:
> 
>>After some juggling, I move the users guide to a new dir (now
>>doc/users_guide - was doc/user_guide).  I also added a preface.
>>Most of it is empty.  You will probably want to update your
>>sandboxes at some point.
> 
> Didn't want to mention this, but since it seems it's not a big problem
> to rename directories -- can you move it to "doc/users_guide/xml"?
> 
> I was hoping you'll do that from the beginning, as you were talking
> about including html version as well.  I don't see a good place to put
> that html version (and txt perhaps) when packaging a release, except
> "doc/users_guide/html" (and "doc/users_guide/txt").

Just to make sure I follow you, you want:

*  nALFS/doc/users_guide/xml - for the xml source.
*  nALFS/doc/users_guide/txt - for a txt rendered version of the xml 
souorce.
*  nALFS/doc/users_guide/html - for a html rendered version of the xml 
source.

That seems to defeat the purpose of cvs.  xml is the source, just like C 
is the source for the program.  I do not see us putting compiled 
binaries of the source in cvs.  Building a source tarball for 
distribution will require more than pulling a tagged version out of cvs. 
  We can do that for the source (to a ceratin extent), but we will need 
to do more work to get the docs in there.  I will need to 
generate/render two books (so far) into html, txt, pdf, and whatever 
else we want to put into the source tarball.  These don't need to be 
kept in the repository IMHO.

For the tarball, I can see us having /doc/users_guide/{html,txt,pdf} and 
/doc/syntax_doc/{html,txt,pdf} with makefiles for installing what you 
want in there (see my conversation with Kevin earlier).

Thoughts?
James




More information about the alfs-log mailing list