Re: modified cvs

[Noel L Yap]

Or, if you're going to modify anything, you can add a CVSPATH ev that's a
generalization of CVSROOT.

Noel




address@hidden on 2001.05.01 16:56:42

Please respond to address@hidden

To:   address@hidden
cc:   address@hidden (bcc: Noel L Yap)
Subject:  Re: modified cvs




[ On Tuesday, May 1, 2001 at 21:52:13 (+0200), nidelet thomas wrote: ]
> Subject: Re: modified cvs
>
> > [ On Tuesday, May 1, 2001 at 15:42:46 (+0200), tom wrote: ]
> > > Subject: modified cvs
> > >
> >
> > If your server system doesn't support ACLs perhaps you can look at
> > schemes of dividing projects up into separate repositories so that you
> > don't need one group-ID for every separate project.
>
> the problem is that i don't want to have a lot of CVSROOT, and it is not
> only me there are other people whom have to checkout every project. But i
> have modified cvs and it is working.
> But it's true i'd rather find a way to do it with the original cvs.
> But Freebsd doesn't support totally the ACLs yet...

Why are you afraid of having multiple repositories?  They work very well
and are trivial to use.  You *only* need to know which repository to use
when doing the initial checkout of a module -- after that it's all
automatic.

I think if you do your layout design correctly it'll also only be those
people who need to check out every project who need to even know about
the existance of multiple repositories.

--
                                   Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>

_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs







This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.