Re: [viewvc-dev] viewvc.branches, viewvc.tags

Philip M. Gollucci wrote:
> Since I'm looking at it again for $work,
> 
> These tables are never populated....
> 
> I tried to do this last year (see archives) based on regexp's given
> 
> /repo/parent/child/{trunk,branches,tags}/
> /repo/module2/{trunk,branches,tags}/
> /repo/module1/{trunk,branches,tags}/
> 
> Which while fairly typical and the redbean way is not a requirement, as 
> such it wasn't included.  I'm thinking its beneficial for me to try again.  
> What is the <quote>correct</quote> way to proceed to do this ?

That's a great question, and this is a great forum for discovering the answer.

There are three related topics here (2 required, 1 optional):

    1. the behavior of the svndbadmin script [required]
    2. the behavior of the ViewVC query interface [required]
    3. the behavior of other aspects of ViewVC [optional]

I think in any case, you first need a flexible way of describing the 
directory topology for a given root.  Already we run into the first 
annoyance:  svndbadmin doesn't consult ViewVC's configury for much of 
anything.  That's probably easy to fix, though.  And I've been toying with 
the idea of making ViewVC support per-root and per-version-control-system 
options anyway, so maybe this is yet another motivator for that change.

So, assuming we have a nice configury way to describe the layout, let's talk 
behaviors.  What does svndbadmin do with this information?  Does it merely 
populate the branches/tags tables?  Does it also munge all the commit paths 
so they they appear to be absolute but are actually relative to the 
/trunk/branch/tag?  If so, what does it do with files that don't live inside 
one of those branch streams?

-- 
C. Michael Pilato <[email protected]>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFINu3hokEGqRcG/W4RAhEyAKC8rFCgFzBxljV1UCqDmFqZuGlAAgCgj6lQ
HX6J+Ke0/LZdbGRByBAlKFI=
=t2a7
-----END PGP SIGNATURE-----