RE: [viewvc-users] Problems with Initial Setup

Much more helpful. When you know if it needs to go to the direct path with the binaries vs. the root path it makes all the difference. Most config files use default install paths to make this clearer, but having comments in the config would be just as easy.

Thanks,

Eric

-----Original Message-----
From: C. Michael Pilato [mailto:[email protected]] 
Sent: Wednesday, September 09, 2009 9:04 AM
To: Eric McCarty
Cc: [email protected]
Subject: Re: [viewvc-users] Problems with Initial Setup

C. Michael Pilato wrote:
> Eric McCarty wrote:
>> Actually I was able to fix the issue by setting the following from 0, 
>> to 1.  I have absolutely no idea why this worked but since it seemed 
>> the problem was that I couldn't fire up the RCS utilities, it was 
>> worth a try, and it panned out. Spiffy experimental feature.
> 
> It worked because 'use_rcsparse' actually tells ViewVC to *not* use 
> the CVSNT program or RCS utilities, but to instead use a Python-based 
> RCS file parser that ships with ViewVC.
> 
>> One thing I do have to say is that ViewVC's documentation is pretty 
>> damn bad. When you say "set var=" to the directory your 
>> ViewVC/RCS/CVS/etc. is pointed to; they need to give an example since 
>> you don’t know if its c:\rcs or c:\rcs\bin, c:\rcs\bin\win32, etc. 
>> Just my .02 from setting it up with no prior knowledge.
> 
> I couldn't agree more.  I think you'll find when/if you upgrade to 
> ViewVC
> 1.1.2 (or better, at the time) that the configuration docs have gotten 
> much, much better.  Still, I take your point about not knowing if "the 
> directory that RCS is installed in" means "the root of where the 
> package dumped all its stuff" or "the directory in which the .exe 
> files directly live".  (By the way, it's the latter in all cases.)

I just committed a change to the sample config files for the 1.1.x and trunk lines of development, turning this explanation:

  ## NOTE:  Options with a "_dir" suffix are for configuring the directories
  ## in which certain programs live; otherwise, the option value should
  ## point to the actual program.

Into this one:

  ## NOTE: Options with a "_dir" suffix are for configuring the
  ## directories in which certain programs live.  Note that this might
  ## not be the same directory into which the program's installer dumped
  ## the whole program package -- we want the deepest directory in which
  ## the executable program itself resides ("C:\rcstools\bin\win32"
  ## rather than just "C:\rcstools", for example).  The values of options
  ## whose names lack the "_dir" suffix should point to the actual
  ## program itself (such as "C:\Program Files\cvsnt\cvs.exe").

and crediting you for the suggestion.  Do you agree that this makes for a significantly more helpful explanation?  (It doesn't apply to the 1.0.x line
unfortunately.)

--
C. Michael Pilato <[email protected]>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

------------------------------------------------------
http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2392987

To unsubscribe from this discussion, e-mail: [[email protected]].