Managing modifications to an open source product

2010-10-14 Thread dan nessett
I develop for a site that uses Mediawiki (MW). We make some modifications to it before deployment. Generally, (using subversion) we check out a tagged version into a workspace, recursively delete the .svn directories, modify a small number of files, add some of our own extensions, and then

RE: Managing modifications to an open source product

2010-10-14 Thread Bob Archer
I develop for a site that uses Mediawiki (MW). We make some modifications to it before deployment. Generally, (using subversion) we check out a tagged version into a workspace, recursively delete the .svn directories, modify a small number of files, add some of our own extensions, and then

Re: Managing modifications to an open source product

2010-10-14 Thread Dan Nessett
On Thu, 14 Oct 2010 15:38:41 -0400, Bob Archer wrote: I develop for a site that uses Mediawiki (MW). We make some modifications to it before deployment. Generally, (using subversion) we check out a tagged version into a workspace, recursively delete the .svn directories, modify a small number

Re: Managing modifications to an open source product

2010-10-14 Thread Olivier Sannier
On 14/10/2010 21:45, Dan Nessett wrote: On Thu, 14 Oct 2010 15:38:41 -0400, Bob Archer wrote: I develop for a site that uses Mediawiki (MW). We make some modifications to it before deployment. Generally, (using subversion) we check out a tagged version into a workspace, recursively delete the

Re: Managing modifications to an open source product

2010-10-14 Thread Stefan Sperling
On Thu, Oct 14, 2010 at 09:55:08PM +0200, Olivier Sannier wrote: On 14/10/2010 21:45, Dan Nessett wrote: On Thu, 14 Oct 2010 15:38:41 -0400, Bob Archer wrote: Generally, (using subversion) we check out a tagged version into a workspace, recursively delete the .svn directories, modify a small

Re: Managing modifications to an open source product

2010-10-14 Thread Dan Nessett
On Thu, 14 Oct 2010 22:33:04 +0200, Stefan Sperling wrote: On Thu, Oct 14, 2010 at 09:55:08PM +0200, Olivier Sannier wrote: On 14/10/2010 21:45, Dan Nessett wrote: On Thu, 14 Oct 2010 15:38:41 -0400, Bob Archer wrote: Generally, (using subversion) we check out a tagged version into a

Re: Managing modifications to an open source product

2010-10-14 Thread Dan Nessett
On Thu, 14 Oct 2010 21:17:59 +, Dan Nessett wrote: On Thu, 14 Oct 2010 21:55:08 +0200, Olivier Sannier wrote: On 14/10/2010 21:45, Dan Nessett wrote: On Thu, 14 Oct 2010 15:38:41 -0400, Bob Archer wrote: I develop for a site that uses Mediawiki (MW). We make some modifications to it

Re: Managing modifications to an open source product

2010-10-14 Thread Geoff Hoffman
Dan, This isn't that much help but are you aware that svn export is exactly the same as svn checkout run a script to delete all the .svn folders ...? The problem with stripping .svn from vendor checkout is then you cannot update it; you're forced to export the whole tree every time. The

Re: Managing modifications to an open source product

2010-10-14 Thread Stefan Sperling
On Thu, Oct 14, 2010 at 09:17:59PM +, Dan Nessett wrote: My question has to do with bypassing the fetch of the complete new MW version into our repository. (NB: MW revisions run about 150MB). Let me describe this in more detail. + When we wish to upgrade to a new MW revision, check out

Re: Managing modifications to an open source product

2010-10-14 Thread Stefan Sperling
On Thu, Oct 14, 2010 at 09:48:21PM +, Dan Nessett wrote: Bad etiquette to answer my own question, but I just reread the Externals Definition section of the book and found this: An externals definition can point only to directories, not to files. So, what I have described won't work