Re: CVS-moular level permisiions ...

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

surya <address@hidden> writes:

Sending MIME encoded text is undesirable for the info-cvs mailing list.
Future e-mail from you encoded in this manner will be ignored.

> Hi Friends,
>
> I am working CVS .I need Small Help for you people .I am planning to create
> Centeral CVS repositroy fro my software group.I am giving the detials below..
>
> /SOFTWARE
>         |
>         // ABC
>                        |        |
>                    ///XYZ    ///PQR
>                                          |
>                                 --------------------------------------------
>                                 ///MNP   ////RST       ////CDE      ////IJK

Use of upper-case names and odd notation may indicate that you are
possibly more interested in a Windows environment. You may wish to
consider http://www.cvsnt.org/ if this is the case.

Ascii Art is not necessarily useful in displaying a hierarchy.

      software
      software/abc
      software/abc/xyz
      software/abc/pqr
      software/abc/pqr
      software/abc/nmp
      software/abc/mnp/rst
      software/abc/mnp/cde
      software/abc/mnp/ijk

> i HAVE TO CREATE lIEK THIS STYRCUTURE Each folder Recognize one
> project -oulde /submodule.I would like to give the permision ( acces
> authentication ) to
> modular Level ..
> i.e.
> /SOFTWARE has to acces by all
> next  //abc module has to accessible by only 'abc' group
> then ///PQR has to access by only 'pqr ' only
> then  //// MNP  has to acces by only 'mnp'
> like this modular permission has to kepy for each and & every folder ..

Use your operating system permissions for this purpose on the
directories you setup.

Some folks have found the following:

   http://sarovar.org/projects/cvspermissions/

useful.

See also

  http://lists.gnu.org/archive/html/info-cvs/2004-08/msg00146.html

You may find it difficult to manage a hierarchy with multiple
permissions as a lockout of one will likely stop your ability to
continue checkouts of files you do have access to. So, you may have to
read up on 'modules' and set things up so that the top-level modules
have the appropriate permissions for a particular user or group and that
you use aliases for mixing multiple modules into one tree.

To be honest, I think your management is borderline insane to consider
the kind of permissions you will be attempting to use. Hire employees
you trust, it is a lot cheaper in the long run.

> could please help in this regards.,
> Thanks
> Help appricated
> surya

        Good luck,
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD4DBQFBc2Fy3x41pRYZE/gRAinFAJ0QIqIGh2vh+lVgkOanHCbxSRksTgCY+m+U
GmR2cvGMEa4Q8rn3W3nVhg==
=16zQ
-----END PGP SIGNATURE-----