Re: Remote CVS and CVSROOT/editinfo scripts requiring tty input

[Howard Zhou]

I have encountered the same problem. verifymsg doesn't help much since it
doesn't allow you to modify cvs log. The only workaround I can think of is
to create a wrapper script to interact with the users first for all possible
commit files(you can do that with cvs status -R) and then checking each file
set based on directory in a batch mode using -m option to the commit.

However you have to take the consideration the wrapper script runs locally
and not depending on any resource on $CVSROOT which is on the remote server.
Also the script has to be accessible to the local client host.

Howard

----- Original Message -----
From: "Larry Jones" <address@hidden>
To: "Mike McKay Jr." <address@hidden>
Cc: <address@hidden>
Sent: Wednesday, January 24, 2001 7:38 AM
Subject: Re: Remote CVS and CVSROOT/editinfo scripts requiring tty input


> Mike McKay Jr. writes:
> >
> > I have scripts specified from CVSROOT/editinfo that require user input
> > during a commit (the perl script does something like "$answer =
> > <STDIN>").  These scripts work fine using local CVS.  However, when I
> > use remote CVS (using ssh), the scripts do not prompt the user for
> > info.
>
> http://www.cvshome.org/docs/manual/cvs_18.html#SEC167:
>
> Note: when CVS is accessing a remote repository, or when the
> `-m' or `-F' options to cvs commit are used, `editinfo' will not
> be consulted. There is no good workaround for this; use
> `verifymsg' instead.
>
> Unfortunately, the advice given in the last line isn't really applicable
> here because verifymsg runs on the server so you still can't interact
> with the user.  What exactly are you trying to do?
>
> -Larry Jones
>
> This sounds suspiciously like one of Dad's plots to build my character.
> -- Calvin
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
>