Re: [Savannah-hackers] Mail transport problem from subversions to gnu.org

[Jaime E . Villate]

On Fri, Mar 23, 2001 at 05:15:29PM +0100, address@hidden wrote:
> 
>  > > I have no clue how to do this in a clean way (in a way that the
>  > > modified log_accum + prep_commit can be contributed back to the CVS
>  > > source tree). Do you have ideas on this subject ?
>  > 
>  > If I understood you correctly (?) I would configure the cvs server to check
>  > out a local copy of whatever enters /subversions/cvs/common/cvsadmin/ and 
> then
>  > use elsewhere the scripts in that local directory, instead of the scripts 
> in
>  > /usr/local/bin as is being currently done. That way we keep the 
> configuration
>  > in sync with the cvs repository, and the developers can change the
>  > configuration without having to ask the administrators.
> 
>  I do not understand this. Could you rephrase in more words, with examples
> maybe ? 

I'll try to explain better what I propose:

1- I update log_accum and commit_pre in my copy of the old cvs (there are
copies of them in admin/ and test/) and commit the changes.

2- in subversions, I create a directory, for example /usr/local/cvsadmin,
login locally in the cvs server, and check out a copy of the directory admin/
in the directory I just created.

3- We would then have to update the loginfo and commit info in the CVSROOT
directories of the 3 repositories, to substitute /usr/local/bin/log_accum and
/usr/local/bin/commit_pre changing the path to /usr/local/cvsadmin

4- Finally, I would add another rule to CVSROOT/loginfo in the old cvs
repository, which would be something like this:

^admin (date; cat; (sleep 2; cd /usr/local/cvsadmin;cvs -q -l update -dP) &)>> 
$CVSROOT/CVSROOT/updatelog 2>&1

to make sure that the local copy in /usr/local/cvsadmin gets update everytime
the repository is updated.
I use this procedure in a server where I host several projects.

Jaime