[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Nested Subversion Checkout

From: Olivier Dagenais <olivier.dagenais_at_formark.com>
Date: 2007-05-15 14:15:11 CEST

> I see what you are trying to suggest. I had never thought of it that
> way. The problem I see with that method is that the other package that
> gets inserted into the site gets changed as much if not more then the
> site itself and when it was updated I would have to commit it to the
> 15 repositories that use that software.

Not necessarily. It can be the responsibility of the maintainers of THOSE repositories to go fetch an update to the package, when they are ready to do so. In other words, do the sites _really_ need to update each and every time the package changes or could they wait a little longer and get a bunch of updates as a batch, perform some integration testing and then commit when they determine the update is good? I'm not suggesting extending this delay to weeks, but maybe somewhere between once a week and once a day. (or on a need-to basis)

> An export had totally slipped my mind (I am new to subversion). For a
> website then, would it not be better to do only an export of both
> repositories, since that way the website will not contain any svn
> files at all?

Definitely: exports are designed for deployment. I was also suggesting an export of the "nested" piece to avoid having Subversion say you can't mix working copies, but that only works if you (or anybody that works on the branded repositories) don't have to make changes to the "core" (a.k.a. "package", "standard", etc.) from within their respective repositories. That's pretty much the difference between my two suggestions and which one you pick will depend on how often the pieces change relative to each other (they may change really fast NOW, but in 2 months? 6 months?? A year???), how often must the branded repositories update the core and the likelihood of changes/customizations to the core on a per-branding basis. Take a look at the "Vendor branches" section of the documentation http://svnbook.red-bean.com/en/1.1/ch07s05.html

There's also a third option that I didn't suggest because you said the branded versions were kept in separate repositories, but if they weren't, an "update" of the core in the branded projects would be a Subversion delete & copy (if changes are never made in the branded versions) or, even better, a merge.

Come to think of it, it looks like the concept of "externals" might be what you were after in the first place: http://svnbook.red-bean.com/en/1.1/ch07s04.html If so, sorry for the added confusion, but at least you'll have more information to make your decision. :)


Olivier Dagenais
Software Engineering / Génie logiciel
Formark - Combine the Best of SharePoint® and Livelink®
Phone: 613-599-5173 ext 238
Make sure you don't miss anything: subscribe to the Formark Newsletter:
Received on Tue May 15 14:13:25 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.