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

Philip M. Gollucci wrote:
> C. Michael Pilato wrote:
>> Philip M. Gollucci wrote:
>>> Since I'm looking at it again for $work,
> 
>> 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.
> Maybe.... can't we start out less grandios?  We could just do
> with re.compile ---
> 
> branch=$1  if   path =~ /branches/([^/])+/
> tag=$1     if   path =~ /tags/([^/])+/
> trunk=true if   path =~ /trunk/
> else
> commit.SetBranch(None)
> 
> That should work regardless of the layout chosen...

If by "work" you mean it won't croak, sure.  But for other definitions of 
"work", I don't see how it can "regardless of the layout chosen".  The 
chosen layout is the very sticking point we're talking about -- ignoring it 
doesn't make the problem go away.

Yes, in many repositories, you'll find /trunk, /tags, and /branches.  But in 
many others, you'll find something different (maybe different projects in 
the root, with the trunk/tags/branches underneath them).

>> 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?
> At a minimum yes, b/c thats all I really need at the moment I think.... :)

Fair 'nuff.

>>  Does it also munge all the commit paths so they they appear to be 
>> absolute but are actually relative to the /trunk/branch/tag?  
> What does this get you ? Why ?

This gets you the ability to treat changes to /trunk/foo and 
/branches/my-branch/foo and /tags/foo as all related to the same item (foo), 
just on different branches.  This brings parity with CVS, where branches and 
tags are orthogonal to path-space.

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

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

iD8DBQFIRZH2okEGqRcG/W4RAlAgAJ9yYV5DJyJiQCggBXkFN7NsbRx2vACfZdfL
d8/EDL6yvKUrQ634b4x60f8=
=tnNt
-----END PGP SIGNATURE-----