You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Geert van Horrik <ge...@catenalogic.com> on 2010/02/18 14:44:45 UTC

SVNParentPath + Recurse (or recursive)

Hi all,

Is this feature planned on the roadmap? I have seen a lot of requests on the internet about this feature. What I want is this:

/svn
/svn/companies
/svn/companies/mycompany
/svn/companies/mycompany/product1 *
/svn/companies/mycompany/product2 *
/svn/companies/mycompany/product3 *
/svn/companies
/svn/companies/theircompany
/svn/companies/theircompany/product1 *
/svn/companies/theircompany/product2 *
/svn/companies/theircompany/product3 *

All items with a * should be a repository.

I don't want to create a custom apache location element, since I need to restart apache each time I modify that one. What I want is just one root folder (/svn) that contains all my repositories, whether they are or are not located directly under the parent.

I also don't want to create a repository per company, because I cannot take products out of a repository then (and archive them separately).

For example, see this patch<http://svn.haxx.se/dev/archive-2007-12/0273.shtml>.

Best regards,
-----
Geert van Horrik


RE: SVNParentPath + Recurse (or recursive)

Posted by Bob Archer <Bo...@amsi.com>.
> On Thu, Feb 18, 2010 at 9:44 AM, Geert van Horrik <ge...@catenalogic.com>
> wrote:
> Hi all,
> 
> Is this feature planned on the roadmap? I have seen a lot of requests on
> the internet about this feature. What I want is this:
> 
> /svn
> /svn/companies
> /svn/companies/mycompany
> /svn/companies/mycompany/product1 *
> /svn/companies/mycompany/product2 *
> /svn/companies/mycompany/product3 *
> /svn/companies
> /svn/companies/theircompany
> /svn/companies/theircompany/product1 *
> /svn/companies/theircompany/product2 *
> /svn/companies/theircompany/product3 *
> 
> All items with a * should be a repository.
> 
> I don't want to create a custom apache location element, since I need to
> restart apache each time I modify that one. What I want is just one root
> folder (/svn) that contains all my repositories, whether they are or are
> not located directly under the parent.
> 
> I also don't want to create a repository per company, because I cannot
> take products out of a repository then (and archive them separately).
> 

I know this isn't what you are asking for. But, rather than have a folder for each company could you using a naming scheme like this:

/svn
/svn/mycompany_product1 *
/svn/mycompany_product2 *
/svn/mycompany_product3 *
/svn/theircompany_product1 *
/svn/theircompany_product2 *
/svn/theircompany_product3 *

It's not as organized but still all the repos for each company will sort together and you only have 1 svn root path this way so you can add repos as needed without needing to edit you apache config.

BOb

Re: SVNParentPath + Recurse (or recursive)

Posted by "Michael P. Reilly" <ar...@gmail.com>.
On Thu, Feb 18, 2010 at 9:44 AM, Geert van Horrik <ge...@catenalogic.com>wrote:

>  Hi all,
>
> Is this feature planned on the roadmap? I have seen a lot of requests on
> the internet about this feature. What I want is this:
>
> /svn
> /svn/companies
> /svn/companies/mycompany
> /svn/companies/mycompany/product1 *
> /svn/companies/mycompany/product2 *
> /svn/companies/mycompany/product3 *
>  /svn/companies
> /svn/companies/theircompany
> /svn/companies/theircompany/product1 *
> /svn/companies/theircompany/product2 *
> /svn/companies/theircompany/product3 *
>
> All items with a * should be a repository.
>
> I don't want to create a custom apache location element, since I need to
> restart apache each time I modify that one. What I want is just one root
> folder (/svn) that contains all my repositories, whether they are or are not
> located directly under the parent.
>
> I also don't want to create a repository per company, because I cannot take
> products out of a repository then (and archive them separately).
>
> For example, see this patch<http://svn.haxx.se/dev/archive-2007-12/0273.shtml>
> .
>
> Best regards,
> -----
> Geert van Horrik
>

I'd like to see this feature as well.  Right now, I'm planning a conversion
from CVS, but because of the organization system, they want to have an
organization similar to this, so some products go in subdirectories of one
repositories, other products go into other repositories - there is logic,
but to get the histories to mesh, they need to be imported all at the same
time, which is a pain point schedule-wise.

It would be much easier if I could have
ReposRoot/prodclassX/productreposA/
                     productreposB/
                     productreposC/
          prodclassY/productreposD/
                     productreposE/
                     ...
                     productreposK/
           ...

  -Michael
-- 
There's so many different worlds,
So many different suns.
And we have just one world,
But we live in different ones.

Re: SVNParentPath + Recurse (or recursive)

Posted by "C. Michael Pilato" <cm...@collab.net>.
Geert van Horrik wrote:
> Hi all,
>  
> Is this feature planned on the roadmap? I have seen a lot of requests on
> the internet about this feature. What I want is this:
>  
> /svn
> /svn/companies
> /svn/companies/mycompany
> /svn/companies/mycompany/product1 *
> /svn/companies/mycompany/product2 *
> /svn/companies/mycompany/product3 *
> /svn/companies
> /svn/companies/theircompany
> /svn/companies/theircompany/product1 *
> /svn/companies/theircompany/product2 *
> /svn/companies/theircompany/product3 *
>  
> All items with a * should be a repository.

I get requests for similar behavior in ViewVC.  I agree that this would be a
convenient feature to offer.  So if you can't find an issue for this already
in our issue tracker[1], please file one.  Be sure to reference this
thread[2] by way of demonstrating developer endorsement.

-- C-Mike

[1] http://subversion.tigris.org/issue-tracker.html
[2] http://svn.haxx.se/users/archive-2010-02/0330.shtml

-- 
C. Michael Pilato <cm...@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand