RE: Changing RCS Directory

[Aaron S. Hawley]

On Fri, 28 Jan 2005, Jason Dickens wrote:

> Thanks,
>
>  I'm working a similar solution. The trick is in identifying the
> filename amid command line options.

well it's always the last thing on the line.  if you're writing a script
in Windows, then that could be difficult.

> It just seems like someone would have put this into RCS by now.

I guess.  But why need a command-line "option" when a command-line
argument works, like you can write a script like this:

#!/bin/sh

ci $* /usr/src/repository/RCS

## END

> Jason
>
> -----Original Message-----
> From: Aaron S. Hawley [mailto:address@hidden
> Sent: Friday, January 28, 2005 2:25 PM
> To: Jason Dickens
> Cc: address@hidden
> Subject: Re: Changing RCS Directory
>
> Are you aware you can specify for some RCS commands both your working
> file
> (the file you wish to check-in or have checked-out to)  and the RCS file
> (the RCS file you want to check-in to, or check-out out from) that you'd
> like to commit it to?
>
> example:
>
> ci file.c /repository/project/src/fun/RCS/file.c
>
> so you could use a wrapper shell script to get your desired
> functionality.
>
> hope this helps,
> /a
>
> On Fri, 28 Jan 2005, Jason Dickens wrote:
>
> > I'm sure this topic has come up before, but the biggest limitation I
> > have to overcome in using RCS is to have the RCS directory local.
> > On UNIX systems this is not much of a problem because symbolic links
> can
> > be used to reference any directory. Windows is a different story.
> >
> > But what I want to know is why don't we have a command line option to
> > put the RCS directory anywhere we want? Then I could alias the basic
> > commands to include this option and our entire network could share the
> > same RCS directory.
> >
> > Sincerely,
> >
> > Jason Dickens
> > Photonic Controls,LLC