Re: CVS like environment?

Sensei wrote:
> My problem is with my students. I provide a .bashrc with useful
> command lines, like
>
> cvslab()
> {
> save old CVSROOT, CVS_RSH, CVSEDITOR
> new CVSROOT & Co
> cvs $@
> restore CVS environment
> unset backup variables
> }
>
> So they can just
>
> cvslab co myProject
> cvslab diff ...
> ...

Why is CVSROOT needed for anything after the checkout? It's not.
This is the same as for subversion. So using this for the other
actions such as diff confuses me.

  cvslab co myProject
  cvs -qn update
  cvs status | grep Status: | grep -v Up-to-date
  cvs diff
  cvs commit

> without caring about the environment... I wanted to do something like
> that for subversion:

You can easily do that for subversion. Since you have already trained
them to use the function calls you can continue.

svnlabco()
{
  svn checkout scheme://host/path/$1 $1
}

Then your students can do:

  svnlabco myProject
  svn status
  svn diff
  svn commit

Bob

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 5 19:22:39 2005