Dev:Subversion - Revision history

Secondplanet at 13:40, 20 February 2011

2011-02-20T13:40:00Z

Zelgadis: moved Subversion to Dev:Subversion

2010-02-22T05:38:32Z

moved Subversion to Dev:Subversion

Zelgadis: Text replace - '{{l|Category:' to '{{Category|'

2010-01-13T16:12:00Z

Text replace - '{{l|Category:' to '{{Category|'

Zelgadis: Text replace - ']]' to '}}'

2009-09-08T07:25:26Z

Text replace - ']]' to '}}'

Zelgadis: Text replace - '[[' to '{{l|'

2009-09-08T05:56:43Z

Text replace - '[[' to '{{l|'

PaulWise: woops, missed one

2008-09-10T07:08:11Z

woops, missed one

PaulWise: update for new svn urls

2008-08-26T01:11:50Z

update for new svn urls

Show changes

PaulWise: typo

2008-01-24T13:41:44Z

typo

PaulWise: I got prematurely excited, svn isn't that flexible

2008-01-24T13:41:21Z

I got prematurely excited, svn isn't that flexible

PaulWise: use the daily-updated tarball, show how to completely ignore dirs and how to rename dirs safely

2008-01-24T00:35:50Z

use the daily-updated tarball, show how to completely ignore dirs and how to rename dirs safely

@@ Line 1: / Line 1: @@
 <!--Categories-->
 {{Category|Building}}
 {{l|Build instructions}} has instructions for checking the source code out of subversion in 3 separate projects, but what if you want a single project?

@@ Line 1: / Line 1: @@
 <!--Categories-->
-{{l|Category:Building}}
+{{Category|Building}}
 {{l|Build instructions}} has instructions for checking the source code out of subversion in 3 separate projects, but what if you want a single project?

@@ Line 1: / Line 1: @@
 <!--Categories-->
-{{l|Category:Building]]
+{{l|Category:Building}}
-{{l|Build instructions]] has instructions for checking the source code out of subversion in 3 separate projects, but what if you want a single project?
+{{l|Build instructions}} has instructions for checking the source code out of subversion in 3 separate projects, but what if you want a single project?
-The easy way is to download the tarball mentioned on the {{l|Source code]] page.  Extract it, and it creates a subversion working directory called 'synfig' which contains ETL, synfig-core and synfig-studio.  'cd' into it and run 'svn up' to update it to the latest version.
+The easy way is to download the tarball mentioned on the {{l|Source code}} page.  Extract it, and it creates a subversion working directory called 'synfig' which contains ETL, synfig-core and synfig-studio.  'cd' into it and run 'svn up' to update it to the latest version.
 Here's how I achieved it.  The following steps will create a new directory called 'code' in the current directory, and put everything inside there.  It's quite long, because I reproduce a bit of the output.  If you just want to see the commands, just to the 'Summary' at the bottom of this page.

@@ Line 1: / Line 1: @@
 <!--Categories-->
-[[Category:Building]]
+{{l|Category:Building]]
-[[Build instructions]] has instructions for checking the source code out of subversion in 3 separate projects, but what if you want a single project?
+{{l|Build instructions]] has instructions for checking the source code out of subversion in 3 separate projects, but what if you want a single project?
-The easy way is to download the tarball mentioned on the [[Source code]] page.  Extract it, and it creates a subversion working directory called 'synfig' which contains ETL, synfig-core and synfig-studio.  'cd' into it and run 'svn up' to update it to the latest version.
+The easy way is to download the tarball mentioned on the {{l|Source code]] page.  Extract it, and it creates a subversion working directory called 'synfig' which contains ETL, synfig-core and synfig-studio.  'cd' into it and run 'svn up' to update it to the latest version.
 Here's how I achieved it.  The following steps will create a new directory called 'code' in the current directory, and put everything inside there.  It's quite long, because I reproduce a bit of the output.  If you just want to see the commands, just to the 'Summary' at the bottom of this page.

@@ Line 121: / Line 121: @@
 Summary:
-  $ svn co http://svn.voria.com/code
+  $ svn co https://synfig.svn.sourceforge.net/svnroot/synfig
   hit Control-C when output begins
   $ svn switch https://synfig.svn.sourceforge.net/svnroot/synfig/ETL/trunk synfig/ETL/

← Older revision	Revision as of 05:38, 22 February 2010
(No difference)

@@ Line 4: / Line 4: @@
 [[Build instructions]] has instructions for checking the source code out of subversion in 3 separate projects, but what if you want a single project?
-The easy way is to download the tarball mentioned on the [[Source code]] page.  Extract it, and it creates a subversion working directory called 'synfig' which contains ETL, synfig and synfigstudio.  'cd' into it and run 'svn up' to update it to the latest version.
+The easy way is to download the tarball mentioned on the [[Source code]] page.  Extract it, and it creates a subversion working directory called 'synfig' which contains ETL, synfig-core and synfigstudio-studio.  'cd' into it and run 'svn up' to update it to the latest version.
 Here's how I achieved it.  The following steps will create a new directory called 'code' in the current directory, and put everything inside there.  It's quite long, because I reproduce a bit of the output.  If you just want to see the commands, just to the 'Summary' at the bottom of this page.
@@ Line 10: / Line 10: @@
 Run this 'co' command.  As soon as you see some output, hit control-c to stop it:
-  /tmp$ svn co http://svn.voria.com/code code
+  /tmp$ svn co http://svn.voria.com/code
   A    code/ETL
   A    code/ETL/releases
@@ Line 62: / Line 62: @@
    U   code/synfig-core
   Updated to revision 440.
 Supposing there are some subdirectories which you don't want at all.  For example, the next up is synfig-docs.  Use control-c again to interrupt the update as soon as it gets started:
@@ Line 113: / Line 105: @@
   A    code/empty
   Updated to revision 440.
 Finally, we're finished.  'du' shows us that only ETL, core, and studio have a significant amount of content: