Difference between revisions of "Dev:Subversion"
m |
m (updated the tarball) |
||
| 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? | [[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 [http://dooglus.rincevent.net/ | + | The easy way is to download [http://dooglus.rincevent.net/random/synfig-r1234.tbz this tarball]. 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. | 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. | ||
Revision as of 07:14, 27 December 2007
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 this tarball. 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.
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 A code/ETL A code/ETL/releases A code/ETL/trunk C-c svn: Caught signal
Notice that subversion was putting all the ETL files inside code/ETL/trunk. We don't want the 'trunk' directory, or any other tags or branches, so we use 'switch' to tell it that. Let the command complete:
/tmp$ svn switch http://svn.voria.com/code/ETL/trunk code/ETL/ D code/ETL/releases D code/ETL/trunk A code/ETL/ETL.pbproj [...] A code/ETL/ETL.prj U code/ETL Updated to revision 440.
Then issue the 'update' command, and again interrupt it when it starts pulling in files:
/tmp$ svn update code A code/synfig-studio A code/synfig-studio/trunk A code/synfig-studio/trunk/synfigstudio.mime.in C-c svn: Caught signal
Again, use 'switch' to tell svn we only want the trunk:
/tmp$ svn switch http://svn.voria.com/code/synfig-studio/trunk code/synfig-studio/ D code/synfig-studio/trunk A code/synfig-studio/synfigstudio.mime.in [...] A code/synfig-studio/bootstrap U code/synfig-studio/ Updated to revision 440.
And repeat again for synfig-core:
/tmp$ svn update code A code/synfig-core A code/synfig-core/trunk A code/synfig-core/trunk/synfig-core.xcodeproj C-c svn: Caught signal
Use switch to select only synfig-core's trunk:
/tmp$ svn switch http://svn.voria.com/code/synfig-core/trunk code/synfig-core/ D code/synfig-core/trunk A code/synfig-core/synfig-core.xcodeproj [...] A code/synfig-core/examples/candy.sif 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:
/tmp$ svn update code A code/synfig-docs A code/synfig-docs/trunk A code/synfig-docs/trunk/en C-c svn: Caught signal
Instead of switching to the trunk, this time we'll switch to 'code/empty', which is an empty directory. This will result in the whole of the synfig-docs/ being ignored:
/tmp$ svn switch http://svn.voria.com/code/empty code/synfig-docs/
D code/synfig-docs/trunk Updated to revision 440.
Proceed in the same manner for the remaining directories. I didn't want either of the OSX trees, so I switched those to 'empty' too:
/tmp$ svn update code A code/gtkmm-osx A code/gtkmm-osx/trunk A code/gtkmm-osx/trunk/gtkmm-meta.mpkg C-c svn: Caught signal
/tmp$ svn switch http://svn.voria.com/code/empty code/gtkmm-osx/ D code/gtkmm-osx/trunk Updated to revision 440.
/tmp$ svn update code A code/synfig-osx A code/synfig-osx/trunk A code/synfig-osx/trunk/launcher C-c svn: Caught signal
/tmp$ svn switch http://svn.voria.com/code/empty code/synfig-osx/ D code/synfig-osx/trunk Updated to revision 440.
/tmp$ svn update code A code/autobuild A code/autobuild/trunk A code/autobuild/trunk/Makefile 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:
/tmp$ du -sk code/* 44 code/autobuild 16 code/empty 3604 code/ETL 16 code/gtkmm-osx 95628 code/synfig-core 16 code/synfig-docs 16 code/synfig-osx 15420 code/synfig-studio /tmp$
Summary:
$ svn co http://svn.voria.com/code hit Control-C when output begins $ svn switch http://svn.voria.com/code/ETL/trunk code/ETL/ $ svn update code hit Control-C when output begins $ svn switch http://svn.voria.com/code/synfig-studio/trunk code/synfig-studio/ $ svn update code hit Control-C when output begins $ svn switch http://svn.voria.com/code/synfig-core/trunk code/synfig-core/ $ svn update code hit Control-C when output begins $ svn switch http://svn.voria.com/code/empty code/synfig-docs/ $ svn update code hit Control-C when output begins $ svn switch http://svn.voria.com/code/empty code/gtkmm-osx/ $ svn update code hit Control-C when output begins $ svn switch http://svn.voria.com/code/empty code/synfig-osx/ $ svn update code
