Re: [viewvc-dev] viewvc.conf "forbidden" has no affect ?

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.

Phil


C. Michael Pilato wrote:
> Phil Pinkerton wrote:
>> I tried forbidden = C
>>
>>  no luck same results.
>
> I should have clarified that 'forbidden' is matching against top-level 
> directories inside a repository.  If in your case ~/svn/repository/C 
> is itself a repository (instead of "C" being a versioned path inside 
> the repository ~/svn/repository), then 'forbidden' will do nothing for 
> you.
>
>> Does viewvc.conf get accessed each time ViewVC is accessed ?
>
> Yes.
>


-- 
" 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]