Getting Started/Build/Windows/subversion - Revision history

Odysseus: moved Getting Started/Build/KDE4/Windows/subversion to Getting Started/Build/Windows/subversion: Reorg, we only have KDE4 now so it's redundant

2011-03-03T10:46:27Z

moved Getting Started/Build/KDE4/Windows/subversion to Getting Started/Build/Windows/subversion: Reorg, we only have KDE4 now so it's redundant

Odysseus at 14:03, 1 March 2011

2011-03-01T14:03:08Z

Odysseus at 14:00, 1 March 2011

2011-03-01T14:00:40Z

Wrohdewald: how to make Pageant automatically reload keys at startup

2011-01-08T06:27:56Z

how to make Pageant automatically reload keys at startup

Wrohdewald: SVN_SSH as an alternative to editing the svn config file

2011-01-07T16:21:37Z

SVN_SSH as an alternative to editing the svn config file

Wrohdewald: tunnel for svn: call it ssh, not putty. And fix spelling for PuTTY

2011-01-07T14:14:04Z

tunnel for svn: call it ssh, not putty. And fix spelling for PuTTY

Xevix: /* Configure Subversion PuTTY Tunnel */ Update to include that username needs to be entered, else this will not work.

2010-03-26T07:58:14Z

‎Configure Subversion PuTTY Tunnel: Update to include that username needs to be entered, else this will not work.

Tampakrap at 09:30, 12 November 2009

2009-11-12T09:30:08Z

Tampakrap at 15:04, 11 August 2009

2009-08-11T15:04:15Z

Tampakrap: use %appdata% instead so it works with vista as well

2009-01-30T22:00:08Z

use %appdata% instead so it works with vista as well

← Older revision		Revision as of 14:03, 1 March 2011
Line 1:		Line 1:
−	{{warning\|This page is yet to be reviewed for changes required by the migration to Git. Information and commands on this page may no longer be valid and should be used with care.}}	+	{{warning\|This page is yet to be reviewed for changes required by the migration to Git. Information and commands on this page may no longer be valid and should be used with care. Please see the [[Development/Git\|KDE Git hub page]] for more details. }}

	This article details how a developer can set up the Subversion command line client <tt>svn</tt> and <tt>PuTTY</tt> on MS Windows to enable write access to the KDE Subversion Repository, using your existing SSH credentials from *nix.		This article details how a developer can set up the Subversion command line client <tt>svn</tt> and <tt>PuTTY</tt> on MS Windows to enable write access to the KDE Subversion Repository, using your existing SSH credentials from *nix.

← Older revision		Revision as of 14:00, 1 March 2011
Line 1:		Line 1:
		+	{{warning\|This page is yet to be reviewed for changes required by the migration to Git. Information and commands on this page may no longer be valid and should be used with care.}}
		+
	This article details how a developer can set up the Subversion command line client <tt>svn</tt> and <tt>PuTTY</tt> on MS Windows to enable write access to the KDE Subversion Repository, using your existing SSH credentials from *nix.		This article details how a developer can set up the Subversion command line client <tt>svn</tt> and <tt>PuTTY</tt> on MS Windows to enable write access to the KDE Subversion Repository, using your existing SSH credentials from *nix.

@@ Line 26: / Line 26: @@
 *Add Pageant to Startup group
 I suggest adding Pageant to the MS Windows Startup group so that it launches every time you start Windows.
 ==Configure Subversion PuTTY Tunnel==

← Older revision		Revision as of 16:21, 7 January 2011
Line 38:		Line 38:

	<tt>plink</tt> is the command line version of PuTTY. <tt>-ssh</tt> tells PuTTY to use SSH protocol. <tt>-C</tt> turns on compression. <tt>-i</tt> is the path to your private key. <tt>-agent</tt> tells PuTTY to try to use Pageant.		<tt>plink</tt> is the command line version of PuTTY. <tt>-ssh</tt> tells PuTTY to use SSH protocol. <tt>-C</tt> turns on compression. <tt>-i</tt> is the path to your private key. <tt>-agent</tt> tells PuTTY to try to use Pageant.
		+
		+	As an alternative to editing the Subversion configuration file, you can define the environment variable SVN_SSH just like you would define the ssh tunnel (untested).

	Now open PuTTY (Start -> All Programs -> PuTTY -> PuTTY) and open a connection to <tt>svn.kde.org</tt> it will ask you if you accept the server id. Select yes,		Now open PuTTY (Start -> All Programs -> PuTTY -> PuTTY) and open a connection to <tt>svn.kde.org</tt> it will ask you if you accept the server id. Select yes,

@@ Line 6: / Line 6: @@
 *Put PuTTY in $PATH
-In order for MS Windows to be able to find PuTTY and its related executable files, you need to add their location to your PATH variable.  By default, puTTY will install to C:\Program Files\PuTTY.  To edit your PATH (for Windows >= Win2k), Start -> Control Panel -> System -> Advanced -> Environment Variables -> System Variables -> Path -> Edit.  Add "C:\Program Files\PuTTY;" to the end of the PATH variable value.
+In order for MS Windows to be able to find PuTTY and its related executable files, you need to add their location to your PATH variable.  By default, PuTTY will install to C:\Program Files\PuTTY.  To edit your PATH (for Windows >= Win2k), Start -> Control Panel -> System -> Advanced -> Environment Variables -> System Variables -> Path -> Edit.  Add "C:\Program Files\PuTTY;" to the end of the PATH variable value.
 ==Enable Existing Key==
@@ Line 13: / Line 13: @@
 *Load into PuTTY Key Generator
-In order to use your OpenSSH private key, you must first convert it to a puTTY Private Key (*.ppk).  To do this, Start -> All Programs -> puTTY -> puTTYgen -> Load.  Browse to wherever you saved your private key (id_dsa) and load it.
+In order to use your OpenSSH private key, you must first convert it to a PuTTY Private Key (*.ppk).  To do this, Start -> All Programs -> PuTTY -> PuTTYgen -> Load.  Browse to wherever you saved your private key (id_dsa) and load it.
 *Save Private Key
@@ Line 28: / Line 28: @@
 ==Configure Subversion PuTTY Tunnel==
-We need to create a new type of tunnel: subversion over puTTY (svn+putty://).
+We need to create a new type of tunnel: subversion over PuTTY (svn+ssh://).
 *We create this tunnel in the Subversion configuration file. Open <tt>%appdata%\Subversion\config</tt>
 *In [Tunnels] section, we create our new tunnel by adding a line (use \\ for backslash):
-<tt>putty = plink -ssh -C -i c:\\path\\to\\id_dsa.ppk -agent <svnaccountname>@svn.kde.org</tt>
+<tt>ssh = plink -ssh -C -i c:\\path\\to\\id_dsa.ppk -agent <svnaccountname>@svn.kde.org</tt>
-<tt>plink</tt> is the command line version of puTTY. <tt>-ssh</tt> tells puTTY to use SSH protocol. <tt>-C</tt> turns on compression. <tt>-i</tt> is the path to your private key. <tt>-agent</tt> tells puTTY to try to use Pageant.
+<tt>plink</tt> is the command line version of PuTTY. <tt>-ssh</tt> tells PuTTY to use SSH protocol. <tt>-C</tt> turns on compression. <tt>-i</tt> is the path to your private key. <tt>-agent</tt> tells PuTTY to try to use Pageant.
-Now open putty (Start -> All Programs -> PuTTY -> PuTTY) and open a connection to <tt>svn.kde.org</tt> it will ask you if you accept the server id. Select yes,
+Now open PuTTY (Start -> All Programs -> PuTTY -> PuTTY) and open a connection to <tt>svn.kde.org</tt> it will ask you if you accept the server id. Select yes,
-a terminal window with an error message may appear, this is normal. If prompted, enter your username. It may then throw errors, but don't worry. The authentication process between your computer and svn.kde.org is now complete, and you may close the putty session.
+a terminal window with an error message may appear, this is normal. If prompted, enter your username. It may then throw errors, but don't worry. The authentication process between your computer and svn.kde.org is now complete, and you may close the PuTTY session.
 ==Repository Access==
-*The repository can now be accessed by using the svn+putty:// tunnel, e.g. <tt>
+*The repository can now be accessed by using the svn+ssh:// tunnel, e.g. <tt>
-C:\KDE4> svn co svn+putty://svn.kde.org/home/kde/trunk/kdesupport/emerge</tt>
+C:\KDE4> svn co svn+ssh://svn.kde.org/home/kde/trunk/kdesupport/emerge</tt>
 ==Setup Git==

← Older revision		Revision as of 15:04, 11 August 2009
Line 43:		Line 43:
	*The repository can now be accessed by using the svn+putty:// tunnel, e.g. <tt>		*The repository can now be accessed by using the svn+putty:// tunnel, e.g. <tt>
	C:\KDE4> svn co svn+putty://svn.kde.org/home/kde/trunk/kdesupport/emerge</tt>		C:\KDE4> svn co svn+putty://svn.kde.org/home/kde/trunk/kdesupport/emerge</tt>
		+
		+	==Setup Git==
		+	Install Git by either running [http://techbase.kde.org/Getting_Started/Build/KDE4/Windows/emerge 'emerge git' ] or by downloading the zip yourself from the [http://code.google.com/p/msysgit/ msysgit page].
		+
		+	After installation you will need to setup the following environment variables (as shown above):
		+	*Create a new variable HOME with value %USERPROFILE%. This will be expanded to the path of your account automatically.
		+	*Create a new variable GIT_SSH with value: plink.exe
		+
		+	Git is now completely setup to follow the steps in the [http://techbase.kde.org/Getting_Started/Sources/KDE_git-tutorial KDE Git tutorial]

@@ Line 30: / Line 30: @@
 We need to create a new type of tunnel: subversion over puTTY (svn+putty://).
-*We create this tunnel in the Subversion configuration file. Open <tt>C:\Documents and Settings\<username>\Application Data\Subversion\config</tt>
+*We create this tunnel in the Subversion configuration file. Open <tt>%appdata%\Subversion\config</tt>
 *In [Tunnels] section, we create our new tunnel by adding a line: