Re: the rcsparse we included

On Tue, Feb 25, 2003 at 09:07:01PM -0600, cmpilato@collab.net wrote:
> Ben Collins-Sussman <sussman@collab.net> writes:
>
> > > If I move the rcsparse package onto my own SVN server, would it be
> > > reasonable to use svn:externals to pick it up from there? Should we keep a
> > > local copy and just resync every now and then? etc.
> >
> > Oooooh, it might be nice to actually exercise svn:externals! It's a
> > feature full of holes.
>
> I was thinking *exactly* that.
>
> Question, though (for Greg). Last time I used cvs2svn, I needed
> rcsparse.py (which I got from my viewcvs CVS working copy), but I also
> needed compat.py. Is that still the case?

Yah, still the case. People aren't seeing it with the rcsparse.py that was
checked in since that is an older rcsparse. But the current rcsparse package
in the ViewCVS repository does require a function from compat.py
(specifically, the compat.timegm() function).

[ note to readers: the compat.py we're talking about is also from ViewCVS ]

There's a comment in viewcvs/lib/vclib/ccvs/rcsparse/common.py about needing
to resolve the compat.py issue. I suspect the answer is to simply replicate
some code.

All righty... it does seem that if I shift the rcsparse package, then we're
all right with setting up an svn:externals reference to it. Once I shift the
code, then I'll bring it up again (I'm thinking within a week, maybe two).

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org