Contribute/First Steps with your KDE SVN Account - Revision history

Aseigo at 08:21, 19 July 2011

2011-07-19T08:21:13Z

Neverendingo: Text replace - "" to ""

2011-06-29T18:30:30Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo at 20:48, 28 June 2011

2011-06-28T20:48:43Z

Neverendingo: Text replace - "
2011-06-28T20:42:25Z

Text replace - "<code" to "<syntaxhighlight"

← Older revision Revision as of 20:42, 28 June 2011
Line 48: Line 48:

You will be asked to accept the SSL certificate on the first attempt to access the server.

You will be asked to accept the SSL certificate on the first attempt to access the server.

−
<code>
+
<syntaxhighlight>

$ svn switch --relocate svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs svn+ssh://username@svn.kde.org/home/kde/trunk/KDE/kdelibs

$ svn switch --relocate svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs svn+ssh://username@svn.kde.org/home/kde/trunk/KDE/kdelibs

The authenticity of host 'svn.kde.org (195.135.221.74)' can't be established.

The authenticity of host 'svn.kde.org (195.135.221.74)' can't be established.

Line 62: Line 62:

The following steps are described using the command line tool <tt>svn</tt>. Personally, I find it better to start with it, as you know immediately where the problems are. Of course, after you have made your first test, you may use whatever tool that you prefer.

The following steps are described using the command line tool <tt>svn</tt>. Personally, I find it better to start with it, as you know immediately where the problems are. Of course, after you have made your first test, you may use whatever tool that you prefer.

−
Then you should be ready to start. The best test is to try to update a small directory. So change to a (small) directory of your local copy of KDE and type: <code bash>svn update</code>
+
Then you should be ready to start. The best test is to try to update a small directory. So change to a (small) directory of your local copy of KDE and type: <syntaxhighlight bash>svn update</code>

Alternatively, if you have no local copies installed, you can just checkout a module.

Alternatively, if you have no local copies installed, you can just checkout a module.

−
<code bash>svn checkout YOUR_URL</code>
+
<syntaxhighlight bash>svn checkout YOUR_URL</code>

Obviously, replace YOUR_URL with the correct path.

Obviously, replace YOUR_URL with the correct path.

Line 84: Line 84:

So maybe you should check your environment variables:

So maybe you should check your environment variables:

−
<code bash>
+
<syntaxhighlight bash>

echo $SVN_EDITOR

echo $SVN_EDITOR

echo $VISUAL

echo $VISUAL

Line 91: Line 91:

Check that their settings suit you for your work with svn. If they do not suit you, check your file {{path|~/.bashrc}} and add something like:

Check that their settings suit you for your work with svn. If they do not suit you, check your file {{path|~/.bashrc}} and add something like:

−
<code bash>export SVN_EDITOR=mcedit</code>
+
<syntaxhighlight bash>export SVN_EDITOR=mcedit</code>

Here it sets mcedit, replace it with your favorite editor. Of course you can set <tt>$EDITOR</tt> instead if you want to change the default editor for you.

Here it sets mcedit, replace it with your favorite editor. Of course you can set <tt>$EDITOR</tt> instead if you want to change the default editor for you.

Odysseus at 14:11, 1 March 2011

2011-03-01T14:11:27Z

Toma: Removed https option. That's no longer possible now.

2010-08-11T21:27:26Z

Removed https option. That's no longer possible now.

Frinring: updated url to document with fingerprints

2010-05-19T17:21:09Z

updated url to document with fingerprints

Chani: /* Commit-Filter */

2010-05-13T02:33:05Z

‎Commit-Filter

PhreakOnALeash: added commit-filter.

2010-05-13T02:28:35Z

added commit-filter.

Blauzahl: /* Notations */ minor grammar change & attempt at clarity by using parallel structure for "KDE's anon and nonanon"

2009-02-05T08:09:48Z

‎Notations: minor grammar change & attempt at clarity by using parallel structure for "KDE's anon and nonanon"

@@ Line 2: / Line 2: @@
 {{improve}}
-This tutorial is about what to do when you are a fresh owner of a new SVN account for KDE.
+This tutorial is about what to do when you are a fresh owner of a new contributor account for KDE.
 == Notations ==
@@ Line 11: / Line 11: @@
 == Preliminary ==
-This tutorial assumes that you have [[Contribute/Get a SVN Account|applied for a KDE SVN account as described here]] and that you have received a positive answer with the information associated with your new account.
+This tutorial assumes that you have [[Contribute/Get a Contributor Account|applied for a KDE Contributor account as described here]] and that you have received a positive answer with the information associated with your new account.
 == Read First! ==
-Now you have a KDE SVN account.
+Now you have a KDE Contributor account.
 Please note that the answer email will have an explanation about how to use the account. (This explanation is also the file [http://websvn.kde.org/trunk/kde-common/svn/svn_instructions.txt?view=markup kde-common/svn/svn_instructions.txt].) It contains also topics not discussed here. So please read this email.
@@ Line 23: / Line 23: @@
 == Changed URLs ==
-Until now, you have worked with one of the anonymous SVN servers. Now that you have a KDE SVN account, you will not use that anonymous server anymore. Therefore the base URL to the SVN server changes for you.
+Until now, you have worked with one of the anonymous servers. Now that you have a KDE Contributor account, you will not use that anonymous server anymore. Therefore the base URL to the SVN server changes for you.
 For the standard anonymous SVN of KDE, it was: {{path|svn://anonsvn.kde.org}} assuming that you have not used an anonymous SVN mirror. If you have used another anonymous SVN server for KDE, then please use its URL instead.

← Older revision		Revision as of 14:11, 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. Please see the [[Development/Git\|KDE Git hub page]] for more details. }}
		+
	{{improve}}		{{improve}}
	This tutorial is about what to do when you are a fresh owner of a new SVN account for KDE.		This tutorial is about what to do when you are a fresh owner of a new SVN account for KDE.

@@ Line 27: / Line 27: @@
 {{Note|If you are unsure which SVN anonymous server you have used, use the <tt>svn info</tt> command to get the server URL.}}
-Now the new base URL for your access to the KDE SVN server depends on which way you have chosen to access it:
+Now the new base URL for your access to the KDE SVN server will be:
-* by HTTPS, it becomes:
- <nowiki>https://username@svn.kde.org/home/kde</nowiki>
-* by SSH, it becomes
   svn+ssh://username@svn.kde.org/home/kde
 where <tt>username</tt> is the name that was given to your KDE SVN account.
@@ Line 41: / Line 38: @@
 Assuming that you are processing the kdelibs module, you have to use:
   svn switch --relocate svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs svn+ssh://username@svn.kde.org/home/kde/trunk/KDE/kdelibs
@@ Line 50: / Line 44: @@
 Be careful on what URLs you type, as SVN will only replace the exact old URL by the exact new URL. So if you mistype one of the URLs, it will not work later. (If you have already fallen into this pitfall, it is not a problem, just use relocate again to replace the wrong URL with the right one.)
-If you connect by HTTPS, as the first relocation will be the first contact to the KDE SVN server with your new SVN account, you will be asked to confirm the SSL certificate of the server and then you will be asked to authenticate yourself.
+You will be asked to accept the SSL certificate on the first attempt to access the server.
-−
-If connecting with svn+ssh, you will be asked to accept the SSL certificate on the first attempt to access the server.
 <code>
@@ Line 63: / Line 55: @@
 Ensure that the fingerprint matches that in the document [http://techbase.kde.org/Getting_Started/Sources/Using_Subversion_with_KDE#The_KDE_repository_structure Using Subversion with KDE]. (Normally, the SHA1 fingerprint is used for HTTPS.)
 == First Test ==
@@ Line 79: / Line 69: @@
 {{note|If you know CVS, you will perhaps wonder that there is no <tt>cvs login</tt>, Subversion has chosen not to have such a way to login. The login is done at the first connection, where authentication is needed.}}
 == Default Editor ==

@@ Line 137: / Line 137: @@
 == Commit-Filter ==
-[http://commitfilter.kde.org/ Commit-Filter] is a service which allows you to monitor folders in SVN for changes, and have each commit's diffs emailed to you. This is useful if you are interested in getting involved in a certain sub-project of KDE and want to keep up with its development.
+[http://commitfilter.kde.org/ Commit-Filter] is a service which allows you to monitor folders (or authors) in SVN for changes, and have each commit's diff emailed to you. This is very useful if you are interested in getting involved in a certain sub-project of KDE and want to keep up with its development.
 == Links ==

← Older revision		Revision as of 02:28, 13 May 2010
Line 135:		Line 135:

	The digest features a small statistics section. To improve the accuracy of those, you should add some information, like age or country, about yourself, which you can do [http://commit-digest.org/data here].		The digest features a small statistics section. To improve the accuracy of those, you should add some information, like age or country, about yourself, which you can do [http://commit-digest.org/data here].
		+
		+	== Commit-Filter ==
		+	[http://commitfilter.kde.org/ Commit-Filter] is a service which allows you to monitor folders in SVN for changes, and have each commit's diffs emailed to you. This is useful if you are interested in getting involved in a certain sub-project of KDE and want to keep up with its development.
		+

	== Links ==		== Links ==

@@ Line 62: / Line 62: @@
 The following steps are described using the command line tool <tt>svn</tt>. Personally, I find it better to start with it, as you know immediately where the problems are. Of course, after you have made your first test, you may use whatever tool that you prefer.
-Then you should be ready to start. The best test is to try to update a small directory. So change to a (small) directory of your local copy of KDE and type: <syntaxhighlight lang="bash">svn update</code>
+Then you should be ready to start. The best test is to try to update a small directory. So change to a (small) directory of your local copy of KDE and type: <syntaxhighlight lang="bash">svn update</syntaxhighlight>
 Alternatively, if you have no local copies installed, you can just checkout a module.

@@ Line 48: / Line 48: @@
 You will be asked to accept the SSL certificate on the first attempt to access the server.
-<syntaxhighlight>
+<syntaxhighlight lang="bash">
 $ svn switch --relocate svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs svn+ssh://username@svn.kde.org/home/kde/trunk/KDE/kdelibs
 The authenticity of host 'svn.kde.org (195.135.221.74)' can't be established.
@@ Line 54: / Line 54: @@
 Are you sure you want to continue connecting (yes/no)? yes
 Warning: Permanently added 'svn.kde.org,195.135.221.74' (RSA) to the list of known hosts.
-</code>
+</syntaxhighlight>
 Ensure that the fingerprint matches that in the document [http://techbase.kde.org/Getting_Started/Sources/Using_Subversion_with_KDE#The_KDE_repository_structure Using Subversion with KDE]. (Normally, the SHA1 fingerprint is used for HTTPS.)
@@ Line 62: / Line 62: @@
 The following steps are described using the command line tool <tt>svn</tt>. Personally, I find it better to start with it, as you know immediately where the problems are. Of course, after you have made your first test, you may use whatever tool that you prefer.
-Then you should be ready to start. The best test is to try to update a small directory. So change to a (small) directory of your local copy of KDE and type: <syntaxhighlight bash>svn update</code>
+Then you should be ready to start. The best test is to try to update a small directory. So change to a (small) directory of your local copy of KDE and type: <syntaxhighlight lang="bash">svn update</code>
 Alternatively, if you have no local copies installed, you can just checkout a module.
-<syntaxhighlight bash>svn checkout YOUR_URL</code>
+<syntaxhighlight lang="bash">svn checkout YOUR_URL</syntaxhighlight>
 Obviously, replace YOUR_URL with the correct path.
@@ Line 84: / Line 84: @@
 So maybe you should check your environment variables:
-<syntaxhighlight bash>
+<syntaxhighlight lang="bash">
 echo $SVN_EDITOR
 echo $VISUAL
 echo $EDITOR
-</code>
+</syntaxhighlight>
 Check that their settings suit you for your work with svn. If they do not suit you, check your file {{path|~/.bashrc}} and add something like:
-<syntaxhighlight bash>export SVN_EDITOR=mcedit</code>
+<syntaxhighlight lang="bash">export SVN_EDITOR=mcedit</syntaxhighlight>
 Here it sets mcedit, replace it with your favorite editor. Of course you can set <tt>$EDITOR</tt> instead if you want to change the default editor for you.

@@ Line 3: / Line 3: @@
 == Notations ==
-* ''SVN'' is used to describe a SVN server, mostly KDE's or the KDE's anonymous SVN servers.
+* ''SVN'' is used to describe an SVN server, mostly KDE's non-anonymous or anonymous SVN servers.
-* The low case word ''svn'' is used to describe the program named svn, which the user can use to access SVN.
+* The lower case word ''svn'' is used to describe the program named svn, which the user can use to access SVN.
 * By ''username'' the name of your KDE SVN account is meant (also known as ''login'').