Re: [viewvc-dev] viewvc.conf "forbidden" has no affect ?
Phil Pinkerton <[email protected]>
| Newsgroups | gmane.comp.version-control.cvs.viewcvs.devel |
|---|---|
| Message-ID | <478F7AF7.1090603__20565.3953169987$1200585516$gmane$org@gmail.com> |
C. Michael Pilato wrote: > 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. :-( > That's not good. Can I contact you directly and discuss the issue with respect to the work I am doing for my client ? (they are also a big Collabnet Client) Best Regards Phil Pinkerton -- " The fundamental principle here is that the justification for a physical concept lies exclusively in its clear an unambiguous relation to the facts it can be experienced" AE --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]