On Fri, 11 Feb 2011, Ron Pinkas wrote:

Hi Ron,

> I fully agree. Can you please explain how it was in done in Harbour
> so we can do the same?

The Harbour conversion was done by Viktor anyhow the whole process
seems to be quite easy for someone using Linux. Windows users will
have to invest some time to setup environment for some tools which
are not available in default system.

As first step it's necessary to download whole CVS repository
(it's not checkout data). SF allows to use rsync so you can make
sth like:

   rsync -av rsync://xharbour.cvs.sourceforge.net/cvsroot/xharbour/* .

Above commands creates full copy of CVS repository in current directory.
Then it's necessary to make the conversion. It can be done using
CVS2SVN tool. It's Python script so it needs Python with some libraries
installed. This script makes conversion and can create new repository
on local disc or on remote SVN server.
I've made small tests and seems that it can convert xHarbour CVS but
it's necessary to force conversion for xharbour-1-2-0 symbol to branch
because it was used as tag in 3013 files and as branch in 1 file
with 1 additional commit in this branch only.
I generated SVN dump file and if you want then I can fully remove
current xHarbour SVN tree and upload this dump file. Then it would
be necessary to commit recent modifications which were not committed
to CVS but only to new SVN repository. I hope this can be done by
their authors - AFAIR only Andi committed some patches.

best regards,
Przemek

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers

Reply via email to