From: Rich Morin <rdm@...>
Date: 2007-03-09T05:15:50+09:00
Subject: Re: having problems fiddling with rake

At 4:48 AM +0900 3/9/07, Jim Weirich wrote:
> The original task uses a rake standard RDocTask.  Of
> the six lines that configure it, three consist of
> selecting the right files (which is the part you want
> to change) and the other three set the document
> directory,  the title and a few options.
>
> Doesn't seem to be too onerous.

The onerous part is keeping track of the library, in
order to look at the file and see if I NEED to make the
changes.  I'm also I'm a bit mystified as to how I'd
(cleanly) change the standard task to get the effect I
want.  I'll try explaining again; perhaps you can help.

I want to be able to have one Rails app generate doc/...
files, based on the file tree of another app.  That is,
the results should appear locally, but the sources should
stay (unmodified) over in the other app.

I don't see six lines (in documentation.rake).  Rather, I
see a long laundry list of "rdoc.rdoc_files.include" calls,
relative to the current directory.  The output files (and
actions such as rm_rf) are also defined in terms of the
current directory.

So, doing a chdir won't help.  I could edit the file to
change the laundry lists, but that seemed onerous to me.
So, I started looking at redefining "include".  How would
you approach this problem, specifically?

-r

P.S.  Still having problems with my include aliasing...
-- 
http://www.cfcl.com/rdm            Rich Morin
http://www.cfcl.com/rdm/resume     rdm@cfcl.com
http://www.cfcl.com/rdm/weblog     +1 650-873-7841

Technical editing and writing, programming, and web development