Why don't you create a subdirectory that you checkout
everything into.
Then from your home directory create symlinks into the subdirectory.
for instance:
cd
mkdir .real_home
cd .real_home
cvs co -d glew glew-home
cd ..
ln -s .real_home/glew-home/.cshrc .cschrc
I would actually write a script t
Andy,
> Why don't you create a subdirectory that you checkout
> everything into.
> ...
> Then from your home directory create symlinks into the subdirectory.
Or just move the CVS directory. Here's a script I use to add files
to my repository. I use it (as root) to maintain my OS config files:
> What was hard about it Greg? I've been using CVS to manage system
> configuration files for two years now. I use a unique repository
> that only root can read/write. The only draw back is that I have CVS
> directories all over my OS. I use Red Hat 6.2 Linux 2.2.14-5.0 and
> CVS 1.10.7.
By t
On Thu, Aug 03, 2000 at 05:49:01PM -0400, Donald Sharp wrote:
> On Thu, Aug 03, 2000 at 01:03:06PM -0700, Glew, Andy wrote:
> > I want to use CVS to version control files in my home
> > directory, such as ~glew-home/.cshrc.
>
> Why don't you create a subdirectory that you checkout
> everything int
done
-Original Message-
From: Donald Sharp [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 03, 2000 2:49 PM
To: Glew, Andy
Cc: [EMAIL PROTECTED]
Subject: Re: CVS'ing home directory files; CVS in place
Why don't you create a subdirectory that you checkout
everything into.
Then f
Andy,
> By the way, are there any funky issues with intermixing
> of checked out directories from different repositories
> in the same directory tree?
Same tree no problem, same directory now that would require some thinking.
How would you get CVS directory to point to two repositories? I've ne
[ On Thursday, August 3, 2000 at 13:03:06 (-0700), Glew, Andy wrote: ]
> Subject: CVS'ing home directory files; CVS in place
>
> This is probably a dumb question, but:
>
> I want to use CVS to version control files in my home
> directory, such as ~glew-home/.cshrc.
You need a build process to ac
> > Why don't you create a subdirectory that you checkout
> > everything into.
> >
> > Then from your home directory create symlinks into the subdirectory.
Not all of the OSes/filesystems I use my common dot-files on have symlinks.
> > E.g. I have already learned that it is not a good idea
> > to have the cvs co flag that creates a CVS directory in the
> > parent of the directory that holds your workspace.
> >
> > (Unfortunately, I can't remember what/where
> > that flag is/was, to remove it.)
>
> That's in CVSROOT/config
> > By the way, are there any funky issues with intermixing
> > of checked out directories from different repositories
> > in the same directory tree?
>
> Same tree no problem, same directory now that would require
> some thinking. How would you get CVS directory to point to two
repositories?
[ On Thursday, August 3, 2000 at 15:29:20 (-0700), Kalle Hoffman wrote: ]
> Subject: Re: CVS'ing home directory files; CVS in place
>
> What was hard about it Greg? I've been using CVS to manage system
> configuration files for two years now. I use a unique repository
>
: Rex Jolliff/YM/RWDOE)
Subject: Re: CVS'ing home directory files; CVS in place
>What was hard about it Greg? I've been using CVS to manage system
>configura
Subject: Re: CVS'ing home directory files; CVS in place
Andy,
>Same tree no problem, same directory now that would require some thinking.
>How would you get CVS directory to point to two repositories?
> If you just use 'su' properly and plain old SCCS or RCS in the actual
> directories where you modify configuration files then you'll have good
> solid CM without the ability to "loose" changes. This is especially
> easy and even trivial if you use a wrapper script on your editor that
> does all
> Not true. if there is a subdirectory that contains files
> from a different repository than its parent and a recursive
> cvs command is executed from the parent, the client will
> not switch repositories during the command
> execution. I havent tried this, but I would guess that the
> best
[EMAIL PROTECTED] writes:
>
> Not true. if there is a subdirectory that contains files from a different
> repository than its parent and a recursive cvs command is executed from
> the parent, the client will not switch repositories during the command
> execution. I havent tried this, [...]
Obv
[EMAIL PROTECTED] (Larry Jones) on 08/04/2000 10:24:28 AM
>[EMAIL PROTECTED] writes:
>>
>> Not true. if there is a subdirectory that contains files from a different
>> repository than its parent and a recursive cvs command is executed from
>> the parent, the client will not switch repositori
[ On Friday, August 4, 2000 at 10:25:00 (-0700), Glew, Andy wrote: ]
> Subject: RE: CVS'ing home directory files; CVS in place
>
> > If you just use 'su' properly and plain old SCCS or RCS in the actual
> > directories where you modify configuration files t
On Fri, Aug 04, 2000 at 09:03:11AM -0700, [EMAIL PROTECTED] wrote:
> Not true. if there is a subdirectory that contains files from a different
> repository than its parent and a recursive cvs command is executed from
> the parent, the client will not switch repositories during the command
> execu
[EMAIL PROTECTED] writes:
>
> Is it a fact that a child directory can be from an
> entirely different remote repository specification (ie username, host and
> repo dir) than a parent and recursive commands will work?
That's certainly the intent.
> Even if this is
> the case I would be wary of u
> From: [EMAIL PROTECTED]
> Date: Fri, 04 Aug 2000 09:00:11 -0700
>
> then at least create a working directory and use make to deploy the
> files into their production locations.
That's how we've been doing it. It's worked quite well for us. The links and
other difficult items are managed in
> [EMAIL PROTECTED] (Larry Jones) on 08/04/2000 11:33:55 AM wrote:
>[EMAIL PROTECTED] writes:
>> Even if this is
>> the case I would be wary of using this ability.
>Why? It has worked from quite some time and there are tests in
>sanity.sh to verify it.
If I cannot recreate the structure eas
Last week I asked about issues CVS'ing one's home directory.
Here's a minor one.
directory/.cvsignore files usually apply locally.
from the manual:
As CVS traverses through your directories,
the contents of any `.cvsignore' will be
appended to the list. The patterns f
[ On Tuesday, August 8, 2000 at 16:13:00 (-0700), Glew, Andy wrote: ]
> Subject: RE: CVS'ing home directory files; CVS in place
>
> ~user/.cvsignore is global, however, applying to
> all CVS work a user does.
>
> In your home directory, these different meanings c
>
> > ~user/.cvsignore is global, however, applying to
> > all CVS work a user does.
> >
> > In your home directory, these different meanings clash.
>
> Yet another good reason why you should always *always* use a "build"
> procedure to install files into their proper place from any arbitrar
[ On Tuesday, August 8, 2000 at 18:42:49 (-0700), Glew, Andy wrote: ]
> Subject: RE: CVS'ing home directory files; CVS in place
>
> Actually, I will happily use a build procedure,
> if it is reversible.
Hmmm reversible...
Do you mean like combining these options to the
> > Subject: RE: CVS'ing home directory files; CVS in place
> >
> > Actually, I will happily use a build procedure,
> > if it is reversible.
>
> Hmmm reversible...
>
> Do you mean like combining these options to the "install" program with
[ On Wednesday, August 9, 2000 at 09:32:14 (-0700), Glew, Andy wrote: ]
> Subject: RE: CVS'ing home directory files; CVS in place
>
> No. I mean "modify the production system in place, and then have
> those changes automatically checked into the repository".
Like I sa
> > Subject: RE: CVS'ing home directory files; CVS in place
> >
> > No. I mean "modify the production system in place, and then have
> > those changes automatically checked into the repository".
>
> Like I said, that's backwards. It's also
On Wednesday, August 9, "Glew, Andy" wrote:
>
> Half of the people here are talking about doing this stuff
> on their LINUX laptops, or on their personal home directories.
> LINUX has meant that thousands of people are now sysadmins.
Bull. Just because you happen to run a Linux box or two does
> > Half of the people here are talking about doing this stuff
> > on their LINUX laptops, or on their personal home directories.
> > LINUX has meant that thousands of people are now sysadmins.
>
> Bull. Just because you happen to run a Linux box or two does
> not make you a sysadmin. If that w
[ On Wednesday, August 9, 2000 at 17:58:57 (-0700), Glew, Andy wrote: ]
> Subject: RE: CVS'ing home directory files; CVS in place
>
> Most "good" sysadmin procedures, like the use of build procedures
> Greg advocates, require quite a bit of effort to set up and mainta
32 matches
Mail list logo
