[PD-dev] repository layout

[IOhannes m zmoelnig]

Winfried Ritsch wrote:
> Hello,
> 
> I just missed the pdconv, so how is the authorization for the repository 
> planed ? Is it possible to restrict access to a subfolder ?

no, since the plan is to stay with sourceforge for now, there is still 
no way to restrict write access to submodules (afaik).

> 
> If so I would recommend to put the trunk, tags, branches as subfolder of  
> projects which can be deligated rather then have a very long list of versions 
> for each external, subexternal or else in one directory. I would prefer:
> 

so how do you like thomas grill's suggestion to do it like
/trunk/pd/
/trunk/externals/iem/comport
/tags/pd/pd-<x>.<y>
/branches/iem/comport-<x>.<y>

the problem with your suggestion i see is, that it is sometimes not 
really clear as to what is a "subproject" and what not.
is it:
/externals/iemlib/iemlib1/[trunk|branches|tags]
or
/externals/iemlib/[trunk|branches|tags]/iemlib1
??


> since it is easy to filter out trunk in path for automatic builds, this should 
> not be a problem and everybody has freedom to organize his projects with tags 
> and branches and subfolder before tags and branches.

well yes, as i have said before this is possible.
but what is the benefit above doing it as one big project in the first 
place, if everybody who wants to checkout more than HEAD of pd-vanilla 
has to resort to setup some filtering (or use meta-projects like 
svn:externals)


and finally: cvs2svn automatically creates one big project, so 
everything else would be extra work :-)

fmasdr
IOhannes