cvs question

I work on a remote repository and the way I access is using ssh. With
CVS, everytime I need to pass this option called 'CVS_RSH' to set the
ssh binary and then can run any cvs operations.

This is sometimes irritating as to I need to remember to set this
variable everytime in my shell(I use hell a lot of terminals).

One way that I thought of was keep a wrapper over the cvs binary itself
which will automatically set the CVS_RSH variable for me or even an
alias would do.

This is kind of per user benefit, what if there are multiple people
working on the same lines of repository access and all have to set their
CVS_RSH variable? Remembering and typing an extra on the commandline
is irky.

I am not a sysadmin, so I cannot do change the system wide cvs binary
changes but I imagine this can be done in .cvsrc file . I know this as
well is a user wide setting, but atleast it would avoid me to type an
extra on the command line.

Any ideas?

Regards,
Nikhil

On Apr 18, 9:20 am, Nikhil <Nik...@nik.com> wrote:
> I work on a remote repository and the way I access is using ssh. With
> CVS, everytime I need to pass this option called 'CVS_RSH' to set the
> ssh binary and then can run any cvs operations.
>
> This is sometimes irritating as to I need to remember to set this
> variable everytime in my shell(I use hell a lot of terminals).
>
> One way that I thought of was keep a wrapper over the cvs binary itself
> which will automatically set the CVS_RSH variable for me or even an
> alias would do.
>
> This is kind of per user benefit, what if there are multiple people
> working on the same lines of repository access and all have to set their
> CVS_RSH variable? Remembering and typing an extra on the commandline
> is irky.
>
> I am not a sysadmin, so I cannot do change the system wide cvs binary
> changes but I imagine this can be done in .cvsrc file . I know this as
> well is a user wide setting, but atleast it would avoid me to type an
> extra on the command line.
>
> Any ideas?

Have your login shell set it in your environment. I use 'bash' so I
added the following line to the '.bash_profile' file in my home
directory:
export CVS_RSH=ssh

DS

Nikhil wrote:
> I work on a remote repository and the way I access is using ssh. With
> CVS, everytime I need to pass this option called 'CVS_RSH' to set the
> ssh binary and then can run any cvs operations.
>
> This is sometimes irritating as to I need to remember to set this
> variable everytime in my shell(I use hell a lot of terminals).
>
> One way that I thought of was keep a wrapper over the cvs binary itself
> which will automatically set the CVS_RSH variable for me or even an
> alias would do.
>
> This is kind of per user benefit, what if there are multiple people
> working on the same lines of repository access and all have to set their
> CVS_RSH variable? Remembering and typing an extra on the commandline
> is irky.
>
> I am not a sysadmin, so I cannot do change the system wide cvs binary
> changes but I imagine this can be done in .cvsrc file . I know this as
> well is a user wide setting, but atleast it would avoid me to type an
> extra on the command line.
>
> Any ideas?
>
> Regards,
> Nikhil

Write yourself a local little shell script, called 'cvsssh' or something like
that. Put it in your $HOME/bin directory, which is usually in your PATH
environment variable, and enjoy.

Then explain to your upstream source control repository that CVS should be
shot like a rabid dog, and they should update to Subversion, at least, if not
git if they have time to get even better tools.

On Apr 19, 4:47*am, Nico Kadel-Garcia <nka...@gmail.com> wrote:
> Nikhilwrote:
> > I work on a remote repository and the way I access is using ssh. With
> >CVS, everytime I need to pass this option called 'CVS_RSH' to set the
> > ssh binary and then can run anycvsoperations.
>
> > This is sometimes irritating as to I need to remember to set this
> > variable everytime in my shell(I use hell a lot of terminals).
>
> > One way that I thought of was keep a wrapper over thecvsbinary itself
> > which will automatically set the CVS_RSH variable for me or even an
> > alias would do.
>
> > This is kind of per user benefit, what if there are multiple people
> > working on the same lines of repository access and all have to set their
> > *CVS_RSH variable? *Remembering and typing an extra on the commandline
> > is irky.
>
> > I am not a sysadmin, so I cannot do change the system widecvsbinary
> > changes but I imagine this can be done in .cvsrc file . I know this as
> > well is a user wide setting, but atleast it would avoid me to type an
> > extra on the command line.
>
> > Any ideas?
>
> > Regards,
> >Nikhil
>
> Write yourself a local little shell script, called 'cvsssh' or something like
> that. Put it in your $HOME/bin directory, which is usually in your PATH
> environment variable, and enjoy.
>
> Then explain to your upstream source control repository thatCVSshould be
> shot like a rabid dog, and they should update to Subversion, at least, if not
> git if they have time to get even better tools.


Actually yes... but CVS is what I have to live with. Although I have
put an alias over cvs command for myself, no wrapper, no explicit
exporting of variable.
but I was more curious if there is any sorts to do with .cvsrc file if
not, if not it brings up a question for an RFE into cvs ... right ;-) ?