[CWB] Sourceforge Updated: how to use the new Subversion system

[Hardie, Andrew]

Hi all,

I have just accepted a software upgrade on the CWB project site that is being rolled out across SourceForge.

Mostly, the only thing this affects is the appearance of the project site on sourceforge.net. HOWEVER, there is one big exception to this - post-upgrade the Subversion system is totally different. 

If your only use of SVN is to check out the code, build and use (i.e. most people), then your course is simple - before the next time you build, delete your current code folder, and then do a new checkout/export - then build from that. The new instructions for doing checkouts are on http://cwb.sf.net now.

If you have local modifications to your CWB code, or if you are working on development (Hi Stefan!), or if you run CQPweb from a live check-out (the easiest way to get updates), then you will need to switch over to the new system using the instructions below.


BROWSING THE CODE
=================

Code-browsing is now done at this address:

https://sourceforge.net/p/cwb/code/

The old addresses still work, but won't permanently, I should imagine.

I have noted that recent commits take a little while (hour or two) to show up here in the code browser.


HOW TO MOVE YOUR LOCALLY-CUSTOMISED CHECKOUT OF CWB ACROSS TO THE NEW SYSTEM
============================================================================

In the folder containing your CWB checkout folder (which I will assume is called "CWB"), do the following:

mv CWB _CWB
svn checkout http://svn.code.sf.net/p/cwb/code/cwb/trunk CWB

(Stefan and others with write access - use https instead of and specify --username=your_SF_username).

Now, copy your local modifications from _CWB to CWB. Then you can delete _CWB.

The same process applies to the CWB perl modules or to branches - just follow the procedure as given with alternative file paths.


HOW TO GET YOUR CQPWEB BACK IN SYNC IF IT IS BASED ON A LIVE CHECKOUT
=====================================================================

NOTE: if you are not interested in keeping up to date with commits to the bleeding-edge CQPweb, you don't need to do this.

Go to the folder containing your main CQPweb folder (which I will assume is called "cqpweb"). Run the following commands, adjusting the name of the folder as appropriate.

(this requires you to be logged on as a user with rights over the CQPweb folder - e.g. the web-server user, usually either www or www-data. If you are a different user, you may need to use su / sudo, and in that case, you may need to change ownership of the new CQPweb directory to the web user later on).

mv cqpweb _cqpweb
svn checkout http://svn.code.sf.net/p/cwb/code/gui/cqpweb/trunk cqpweb
mv _cqpweb/lib/config.inc.php  cqpweb/lib/config.inc.php

Then, move each of your established corpus directories from _cqpweb/ to cqpweb/ . E.g. If you have a corpus "mycorpus1" and "mycorpus2", then do

mv -tcqpweb _cqpweb/mycorpus1 _cqpweb/mycorpus2

(and so on).

Finally (optional) do the following:

rm -r _cqpweb

to remove the old code. DO NOT DO THIS until you are sure you have moved all old corpus files across.


Sorry for the fuss,

best

Andrew.