[ignore that last e-mail, my mail tool crashed]
> 1) The cvs for bsf is currently:
> :pserver:[EMAIL PROTECTED]:/usr/cvs/bsf
> shouldn't this be:
> :pserver:[EMAIL PROTECTED]:/usr/cvs/bsf
It is my workspace! Build your own! ;-)
Seriously, I need to spend some more time on documentation, and more time
factoring the parts that people would most likely want to change from those
that people are less likely to want to change.
One thing that surprises me is that I expected most people to want to build
a different mix of projects than I do, but to date that has not been the
case.
> 2) I _think_ that I've had to manually login to each pserver
> to get an entry in my .cvspass file. Can't the passwords be
> located with the trees for public/anon cvs access?
The way I work is that I stay logged on, so having gump nighly log me off
would not be terribly appealing to me.
The right answer might be an option. But in any case, this will likely be
addressed with the merge with Alexandria as it has the passwords in the
definition.
> 3) I had to alter the gen.sh to get it working under cygwin
> (attached). Sorry it's not a diff - I don't have cvs access at
> work.
You made three changes. The cygpath is clearly a good one.
I'm surprised that "hostname -s" doesn't work for you. It does for me with
cygwin. What problem are you having?
Removing the "./" in front of the shell script is a problem in that many
Unixes don't have the current working directory in the path for security
reasons. Again, what problem are you having? And would "sh puball.sh
$SOURCE" work for you?
> 4) In the cvs co and update requests there's a hard coded -z 3
> flag. Wouldn't this be best just be left to the .cvsrc to control?
It certainly should be moved out of the stylesheets. My preference would
be to place something in the workspace definition that allows one to
specify options.
Historical background: I first wrote these scripts by hand, then I wrote
some XSLT to generate them. When I write scripts, I tend to be very
explicit - specifying defaults whenever possible. When I automated it,
this just sorta got sucked in without much thought.
> 5) Rather than having:
> basedir="/home/rubys/jakarta" cvsdir="/home/rubys/jakarta/cvs"
> wouldn't:
> basedir="~/jakarta" cvsdir="~/jakarta/cvs"
> be more generic for people?
In essence the same answer as for #1. Specifying "~" would mean that there
was less that most people would have to adapt.
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
