Ethereal-dev: Re: [Ethereal-dev] CVS Build Problems

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Gilbert Ramirez <gram@xxxxxxxxxx>
Date: Wed, 22 Nov 2000 06:01:41 -0600
On Wed, 22 Nov 2000 11:16:08 +0000 (GMT)
Neil Hunter <neil.hunter@xxxxxxxxxxxxxxxxxxx> wrote:

> On Wed, 22 Nov 2000, Graham Bloice wrote:
> 
> > Do you have a plugins/mgcp directory ??
> > 
> > I ran across the same problem last weekend after a 'cvs update'.  Guy helped
> > me out with suggesting the -d flag for 'cvs update' which got the missing
> > directory.
> 
> Wahay! That fixed it a treat!
> 
> Not sure why the "-d" sorted out the token, but hey - it works! :)
> 
>

By default, 'cvs update' doesn't add new directories. I don't know if this
is a result of its being based on RCS, which is directory oriented or not.
All I know is that I don't like the default behavior. Whenever a directory
is added to the CVS repository, two things need to happen:

1. The group of the new directory on cvs.ethereal.com needs to change
to 'cvs'. CVS doesn't do this automatically, and it would be awkward
for our default group on cvs.ethereal.com to be cvs, causing any file
that we create on that computer be owned by group 'cvs'.

If the directory's group is not changed, then no one besides the owner of
the file can retrieve it (cvs update, cvs checkout) via cvs.

2. Everyone's local CVS image needs to be updated via 'cvs update -d' to
get the new directory.

--gilbert