Re: [viewvc-dev] viewvc.conf "forbidden" has no affect ?
"C. Michael Pilato" <[email protected]>
| Newsgroups | gmane.comp.version-control.cvs.viewcvs.devel |
|---|---|
| Organization | CollabNet, Inc. |
| Message-ID | <[email protected]> |
Phil Pinkerton wrote: > Michael, > > Thanks it works in that respect but the problem is we have multiple > Repositories with the same path. > > Expanded example: > > ~/svn/repository/A/tags > ~/svn/repository/A/branches > ~/svn/repository/A/trunk > > ~/svn/repository/B/tags > ~/svn/repository/B/branches > ~/svn/repository/B/trunk > > ~/svn/repository/C/tags > ~/svn/repository/C/branches > ~/svn/repository/C/trunk > > So if I use 'forbidden = trunk' then /*all*/ 'trunk' are forbidden. > Which is not the desired result. > > What we want is to be able to select which 'trunk' is forbidden on a by > repository basis. Sadly, today you are out of luck. There is ongoing work in ViewVC's truck to support more flexible path-based authorization, but the work is incomplete. Sorry. :-( -- C. Michael Pilato <[email protected]> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHj2tKokEGqRcG/W4RAonrAKC/AyXfem2/mzxSKi1AC3pmT9W9tgCbBeFh hfhHTA2BUMy9zMAD8lQVsqk= =kFbL -----END PGP SIGNATURE-----