[Live-demo] svn vs. cp

Alex Mandel tech_dev at wildintellect.com
Wed Jan 27 10:59:34 PST 2010

Hamish wrote:
> Hi,
> wrt 'svn co' vs. copying from within the tree-
>> copy config files from checked out svn directory, rather than
>> "wget https://svn.osgeo.org/...xx.config".
> fwiw this makes the individual scripts less useful on their own.
> e.g. a couple of days ago I was testing out one of the install
> scripts on Debian/Lenny, by a rough cut & paste into the
> terminal method, and it was nice to have the patches be
> automatically found on the server.
> having said that, I don't think that is a big deal, either way
> is fine with me...
>> This means we can rebuild old releases (which can't be done at
>> the moment). 
> sure we can, it's already taken care of. I migrated all the
> paths away from trunk as soon as we branched off the old version
> so when we tagged it everything would still work as desired.
> It just took a minute to do with 'sed -i'.
> Hamish

I was thinking mostly about the main_docs script. Since thats an all or
none, a straight cp makes sense to cut down on requests to the svn. I
think within individual scripts warrants more discussion as you pointed out.

Can we script that sed action so that anyone can do it. Personally I
know of sed but not really how to properly use it.

The other idea Cameron and I discussed briefly was moving dev of each
version to a branch/tag at the start of the cycle so those links are
correct to begin with, rather than cleaning up after the end.


More information about the Osgeolive mailing list