KDE TechBase - User contributions [en]

Projects/KDevelop4/DUChainIdentities

2013-01-23T05:06:46Z

Nicolás: KDevPlatform → Platform

This is a list of Identity values used by various plugins for their Declarations and Types.

{|class="wikitable"
!Category
!ID
!Use
|-
| Platform || 1 || <tt>DUChainBase</tt>
|-
| Platform || 2 || <tt>DUContext</tt>
|-
| Platform || 4 || <tt>TopDUContext</tt>
|-
| Platform || 6 || <tt>AliasDeclaration</tt>
|-
| Platform || 7 || <tt>Declaration</tt>
|-
| Platform || 9 || <tt>ClassMemberDeclaration</tt>
|-
| Platform || 10 || <tt>ForwardDeclaration</tt>
|-
| Platform || 11 || <tt>ParsingEnvironmentFile</tt>
|-
| Platform || 12 || <tt>FunctionDeclaration</tt>
|-
| Platform || 13 || <tt>NamespaceAliasDeclaration</tt>
|-
| Platform || 14 || <tt>ClassFunctionDeclaration</tt>
|-
| Platform || 15 || <tt>Problem</tt>
|-
| Platform || 17 || <tt>ClassDeclaration</tt>
|-
| C++ || 18 || <tt>TemplateParameterDeclaration</tt>
|-
| Platform || 21 || <tt>FunctionDefinition</tt>
|-
| Ruby || 42 || <tt>MethodDeclaration</tt>
|-
| Ruby || 43 || <tt>RubyDUContext<DUContext></tt> (aka <tt>RubyNormalDUContext</tt>)
|-
| Ruby || 44 || <tt>ModuleDeclaration</tt>
|-
| Ruby || 45 || <tt>RubyDUContext<TopDUContext></tt> (aka <tt>RubyTopDUContext</tt>)
|-
| Ruby || 47 || <tt>VariableDeclaration</tt>
|-
| C++ || 52 || <tt>CppDUContext<TopDUContext></tt> (aka <tt>CppNormalDUContext</tt>)
|-
| PHP || 53 || <tt>PhpDUContext<DUContext></tt> (aka <tt>PhpNormalDUContext</tt>)
|-
| C++ || 54 || <tt>CppDUContext<DUContext></tt> (aka <tt>CppTopDUContext</tt>)
|-
| PHP || 55 || <tt>PhpDUContext<TopDUContext></tt> (aka <tt>PhpTopDUContext</tt>)
|-
| C++ || 56 || <tt>SpecialTemplateDeclaration<AliasDeclaration></tt>
|-
| C++ || 57 || <tt>SpecialTemplateDeclaration<Declaration></tt>
|-
| C++ || 59 || <tt>SpecialTemplateDeclaration<ClassMemberDeclaration></tt>
|-
| C++ || 60 || <tt>SpecialTemplateDeclaration<ForwardDeclaration></tt>
|-
| C++ || 62 || <tt>SpecialTemplateDeclaration<FunctionDeclaration></tt>
|-
| C++ || 64 || <tt>SpecialTemplateDeclaration<ClassFunctionDeclaration></tt>
|-
| C++ || 67 || <tt>SpecialTemplateDeclaration<ClassDeclaration></tt>
|-
| C++ || 68 || <tt>SpecialTemplateDeclaration<ClassDeclaration></tt>
|-
| C++ || 71 || <tt>SpecialTemplateDeclaration<FunctionDefinition></tt>
|-
| C++ || 73 || <tt>EnvironmentFile</tt>
|-
| C++ || 74 || <tt>QtFunctionDeclaration</tt>
|-
| C++ || 75 || <tt>QPropertyDeclaration</tt>
|-
| PHP || 80 || <tt><s>ConstantDeclaration</s></tt> (not used anymore)
|-
| PHP || 81 || <tt><s>ClassDeclaration</s></tt> (not used anymore)
|-
| PHP || 83 || <tt>VariableDeclaration</tt>
|-
| PHP || 84 || <tt>ClassMethodDeclaration</tt>
|-
| PHP || 85 || <tt>ClassDeclaration</tt>
|-
| PHP || 86 || <tt>FunctionDeclaration</tt>
|-
| PHP || 87 || <tt>NamespaceDeclaration</tt>
|-
| PHP || 88 || <tt>NamespaceAliasDeclaration</tt>
|-
| XML || 90 || <tt>ElementDeclaration</tt>
|-
| XML || 91 || <tt>ImportDeclaration</tt>
|-
| Python || 100 || <tt>PythonDUContext<TopDUContext></tt> (aka <tt>PythonTopDUContext</tt>)
|-
| Python || 101 || <tt>PythonDUContext<DUContext></tt> (aka <tt>PythonNormalDUContext</tt>)
|-
| C++ || 124 || <tt>SpecialTemplateDeclaration<QtFunctionDeclaration></tt>
|-
| Python || 125 || <tt>ClassDeclaration</tt>
|-
| Python || 126 || <tt>FunctionDeclaration</tt>
|-
| Python || 127 || <tt><s>ClassFunctionDeclaration</s></tt> (not used anymore)
|}

{|class="wikitable"
|+ Types
!Category
!ID
!Use
|-
| Platform || 1 || <tt>AbstractType</tt>
|-
| Platform || 2 || <tt>IntegralType</tt>
|-
| Platform || 3 || <tt>PointerType</tt>
|-
| Platform || 4 || <tt>ReferenceType</tt>
|-
| Platform || 5 || <tt>FunctionType</tt>
|-
| Platform || 6 || <tt>StructureType</tt>
|-
| Platform || 7 || <tt>ArrayType</tt>
|-
| Platform || 8 || <tt>DelayedType</tt>
|-
| Platform || 9 || <tt>TypeAliasType</tt>
|-
| Platform || 14 || <tt>ConstantIntegralType</tt>
|-
| C++ || 18 || <tt>CppClassType</tt>
|-
| Platform || 20 || <tt>EnumeratorType</tt>
|-
| Platform || 21 || <tt>EnumerationType</tt>
|-
| C++ || 23 || <tt>CppTemplateParameterType</tt>
|-
| Platform || 39 || <tt>UnsureType</tt>
|-
| Ruby || 41 || <tt>ClassType</tt>
|-
| C++ || 42 || <tt>PtrToMemberType</tt>
|-
| PHP || 50 || <tt>IntegralTypeExtended</tt>
|-
| PHP || 51 || <tt>StructureType</tt>
|-
| Python || 59 || <tt>IndexedContainer</tt>
|-
| Python || 60 || <tt>IntegralTypeExtended</tt>
|-
| Python || 61 || <tt>VariableLengthContainer</tt>
|-
| Python || 62 || <tt>HintedType</tt>
|-
| Python || 63 || <tt>UnsureType</tt>
|}

Projects/KDevelop4/DUChainIdentities

2013-01-23T04:36:24Z

Nicolás: Add Ruby IDs

This is a list of Identity values used by various plugins for their Declarations and Types.

{|class="wikitable"
!Category
!ID
!Use
|-
| KDevPlatform || 1 || <tt>DUChainBase</tt>
|-
| KDevPlatform || 2 || <tt>DUContext</tt>
|-
| KDevPlatform || 4 || <tt>TopDUContext</tt>
|-
| KDevPlatform || 6 || <tt>AliasDeclaration</tt>
|-
| KDevPlatform || 7 || <tt>Declaration</tt>
|-
| KDevPlatform || 9 || <tt>ClassMemberDeclaration</tt>
|-
| KDevPlatform || 10 || <tt>ForwardDeclaration</tt>
|-
| KDevPlatform || 11 || <tt>ParsingEnvironmentFile</tt>
|-
| KDevPlatform || 12 || <tt>FunctionDeclaration</tt>
|-
| KDevPlatform || 13 || <tt>NamespaceAliasDeclaration</tt>
|-
| KDevPlatform || 14 || <tt>ClassFunctionDeclaration</tt>
|-
| KDevPlatform || 15 || <tt>Problem</tt>
|-
| KDevPlatform || 17 || <tt>ClassDeclaration</tt>
|-
| C++ || 18 || <tt>TemplateParameterDeclaration</tt>
|-
| KDevPlatform || 21 || <tt>FunctionDefinition</tt>
|-
| Ruby || 42 || <tt>MethodDeclaration</tt>
|-
| Ruby || 43 || <tt>RubyDUContext<DUContext></tt> (aka <tt>RubyNormalDUContext</tt>)
|-
| Ruby || 44 || <tt>ModuleDeclaration</tt>
|-
| Ruby || 45 || <tt>RubyDUContext<TopDUContext></tt> (aka <tt>RubyTopDUContext</tt>)
|-
| Ruby || 47 || <tt>VariableDeclaration</tt>
|-
| C++ || 52 || <tt>CppDUContext<TopDUContext></tt> (aka <tt>CppNormalDUContext</tt>)
|-
| PHP || 53 || <tt>PhpDUContext<DUContext></tt> (aka <tt>PhpNormalDUContext</tt>)
|-
| C++ || 54 || <tt>CppDUContext<DUContext></tt> (aka <tt>CppTopDUContext</tt>)
|-
| PHP || 55 || <tt>PhpDUContext<TopDUContext></tt> (aka <tt>PhpTopDUContext</tt>)
|-
| C++ || 56 || <tt>SpecialTemplateDeclaration<AliasDeclaration></tt>
|-
| C++ || 57 || <tt>SpecialTemplateDeclaration<Declaration></tt>
|-
| C++ || 59 || <tt>SpecialTemplateDeclaration<ClassMemberDeclaration></tt>
|-
| C++ || 60 || <tt>SpecialTemplateDeclaration<ForwardDeclaration></tt>
|-
| C++ || 62 || <tt>SpecialTemplateDeclaration<FunctionDeclaration></tt>
|-
| C++ || 64 || <tt>SpecialTemplateDeclaration<ClassFunctionDeclaration></tt>
|-
| C++ || 67 || <tt>SpecialTemplateDeclaration<ClassDeclaration></tt>
|-
| C++ || 68 || <tt>SpecialTemplateDeclaration<ClassDeclaration></tt>
|-
| C++ || 71 || <tt>SpecialTemplateDeclaration<FunctionDefinition></tt>
|-
| C++ || 73 || <tt>EnvironmentFile</tt>
|-
| C++ || 74 || <tt>QtFunctionDeclaration</tt>
|-
| C++ || 75 || <tt>QPropertyDeclaration</tt>
|-
| PHP || 80 || <tt><s>ConstantDeclaration</s></tt> (not used anymore)
|-
| PHP || 81 || <tt><s>ClassDeclaration</s></tt> (not used anymore)
|-
| PHP || 83 || <tt>VariableDeclaration</tt>
|-
| PHP || 84 || <tt>ClassMethodDeclaration</tt>
|-
| PHP || 85 || <tt>ClassDeclaration</tt>
|-
| PHP || 86 || <tt>FunctionDeclaration</tt>
|-
| PHP || 87 || <tt>NamespaceDeclaration</tt>
|-
| PHP || 88 || <tt>NamespaceAliasDeclaration</tt>
|-
| XML || 90 || <tt>ElementDeclaration</tt>
|-
| XML || 91 || <tt>ImportDeclaration</tt>
|-
| Python || 100 || <tt>PythonDUContext<TopDUContext></tt> (aka <tt>PythonTopDUContext</tt>)
|-
| Python || 101 || <tt>PythonDUContext<DUContext></tt> (aka <tt>PythonNormalDUContext</tt>)
|-
| C++ || 124 || <tt>SpecialTemplateDeclaration<QtFunctionDeclaration></tt>
|-
| Python || 125 || <tt>ClassDeclaration</tt>
|-
| Python || 126 || <tt>FunctionDeclaration</tt>
|-
| Python || 127 || <tt><s>ClassFunctionDeclaration</s></tt> (not used anymore)
|}

{|class="wikitable"
|+ Types
!Category
!ID
!Use
|-
| KDevPlatform || 1 || <tt>AbstractType</tt>
|-
| KDevPlatform || 2 || <tt>IntegralType</tt>
|-
| KDevPlatform || 3 || <tt>PointerType</tt>
|-
| KDevPlatform || 4 || <tt>ReferenceType</tt>
|-
| KDevPlatform || 5 || <tt>FunctionType</tt>
|-
| KDevPlatform || 6 || <tt>StructureType</tt>
|-
| KDevPlatform || 7 || <tt>ArrayType</tt>
|-
| KDevPlatform || 8 || <tt>DelayedType</tt>
|-
| KDevPlatform || 9 || <tt>TypeAliasType</tt>
|-
| KDevPlatform || 14 || <tt>ConstantIntegralType</tt>
|-
| C++ || 18 || <tt>CppClassType</tt>
|-
| KDevPlatform || 20 || <tt>EnumeratorType</tt>
|-
| KDevPlatform || 21 || <tt>EnumerationType</tt>
|-
| C++ || 23 || <tt>CppTemplateParameterType</tt>
|-
| KDevPlatform || 39 || <tt>UnsureType</tt>
|-
| Ruby || 41 || <tt>ClassType</tt>
|-
| C++ || 42 || <tt>PtrToMemberType</tt>
|-
| PHP || 50 || <tt>IntegralTypeExtended</tt>
|-
| PHP || 51 || <tt>StructureType</tt>
|-
| Python || 59 || <tt>IndexedContainer</tt>
|-
| Python || 60 || <tt>IntegralTypeExtended</tt>
|-
| Python || 61 || <tt>VariableLengthContainer</tt>
|-
| Python || 62 || <tt>HintedType</tt>
|-
| Python || 63 || <tt>UnsureType</tt>
|}

Projects/KDevelop4/DUChainIdentities

2013-01-23T04:28:55Z

Nicolás: Add XML IDs. Change page description.

This is a list of Identity values used by various plugins for their Declarations and Types.

{|class="wikitable"
!Category
!ID
!Use
|-
| KDevPlatform || 1 || <tt>DUChainBase</tt>
|-
| KDevPlatform || 2 || <tt>DUContext</tt>
|-
| KDevPlatform || 4 || <tt>TopDUContext</tt>
|-
| KDevPlatform || 6 || <tt>AliasDeclaration</tt>
|-
| KDevPlatform || 7 || <tt>Declaration</tt>
|-
| KDevPlatform || 9 || <tt>ClassMemberDeclaration</tt>
|-
| KDevPlatform || 10 || <tt>ForwardDeclaration</tt>
|-
| KDevPlatform || 11 || <tt>ParsingEnvironmentFile</tt>
|-
| KDevPlatform || 12 || <tt>FunctionDeclaration</tt>
|-
| KDevPlatform || 13 || <tt>NamespaceAliasDeclaration</tt>
|-
| KDevPlatform || 14 || <tt>ClassFunctionDeclaration</tt>
|-
| KDevPlatform || 15 || <tt>Problem</tt>
|-
| KDevPlatform || 17 || <tt>ClassDeclaration</tt>
|-
| C++ || 18 || <tt>TemplateParameterDeclaration</tt>
|-
| KDevPlatform || 21 || <tt>FunctionDefinition</tt>
|-
| C++ || 52 || <tt>CppDUContext<TopDUContext></tt> (aka <tt>CppNormalDUContext</tt>)
|-
| PHP || 53 || <tt>PhpDUContext<DUContext></tt> (aka <tt>PhpNormalDUContext</tt>)
|-
| C++ || 54 || <tt>CppDUContext<DUContext></tt> (aka <tt>CppTopDUContext</tt>)
|-
| PHP || 55 || <tt>PhpDUContext<TopDUContext></tt> (aka <tt>PhpTopDUContext</tt>)
|-
| C++ || 56 || <tt>SpecialTemplateDeclaration<AliasDeclaration></tt>
|-
| C++ || 57 || <tt>SpecialTemplateDeclaration<Declaration></tt>
|-
| C++ || 59 || <tt>SpecialTemplateDeclaration<ClassMemberDeclaration></tt>
|-
| C++ || 60 || <tt>SpecialTemplateDeclaration<ForwardDeclaration></tt>
|-
| C++ || 62 || <tt>SpecialTemplateDeclaration<FunctionDeclaration></tt>
|-
| C++ || 64 || <tt>SpecialTemplateDeclaration<ClassFunctionDeclaration></tt>
|-
| C++ || 67 || <tt>SpecialTemplateDeclaration<ClassDeclaration></tt>
|-
| C++ || 68 || <tt>SpecialTemplateDeclaration<ClassDeclaration></tt>
|-
| C++ || 71 || <tt>SpecialTemplateDeclaration<FunctionDefinition></tt>
|-
| C++ || 73 || <tt>EnvironmentFile</tt>
|-
| C++ || 74 || <tt>QtFunctionDeclaration</tt>
|-
| C++ || 75 || <tt>QPropertyDeclaration</tt>
|-
| PHP || 80 || <tt><s>ConstantDeclaration</s></tt> (not used anymore)
|-
| PHP || 81 || <tt><s>ClassDeclaration</s></tt> (not used anymore)
|-
| PHP || 83 || <tt>VariableDeclaration</tt>
|-
| PHP || 84 || <tt>ClassMethodDeclaration</tt>
|-
| PHP || 85 || <tt>ClassDeclaration</tt>
|-
| PHP || 86 || <tt>FunctionDeclaration</tt>
|-
| PHP || 87 || <tt>NamespaceDeclaration</tt>
|-
| PHP || 88 || <tt>NamespaceAliasDeclaration</tt>
|-
| XML || 90 || <tt>ElementDeclaration</tt>
|-
| XML || 91 || <tt>ImportDeclaration</tt>
|-
| Python || 100 || <tt>PythonDUContext<TopDUContext></tt> (aka <tt>PythonTopDUContext</tt>)
|-
| Python || 101 || <tt>PythonDUContext<DUContext></tt> (aka <tt>PythonNormalDUContext</tt>)
|-
| C++ || 124 || <tt>SpecialTemplateDeclaration<QtFunctionDeclaration></tt>
|-
| Python || 125 || <tt>ClassDeclaration</tt>
|-
| Python || 126 || <tt>FunctionDeclaration</tt>
|-
| Python || 127 || <tt><s>ClassFunctionDeclaration</s></tt> (not used anymore)
|}

{|class="wikitable"
|+ Types
!Category
!ID
!Use
|-
| KDevPlatform || 1 || <tt>AbstractType</tt>
|-
| KDevPlatform || 2 || <tt>IntegralType</tt>
|-
| KDevPlatform || 3 || <tt>PointerType</tt>
|-
| KDevPlatform || 4 || <tt>ReferenceType</tt>
|-
| KDevPlatform || 5 || <tt>FunctionType</tt>
|-
| KDevPlatform || 6 || <tt>StructureType</tt>
|-
| KDevPlatform || 7 || <tt>ArrayType</tt>
|-
| KDevPlatform || 8 || <tt>DelayedType</tt>
|-
| KDevPlatform || 9 || <tt>TypeAliasType</tt>
|-
| KDevPlatform || 14 || <tt>ConstantIntegralType</tt>
|-
| C++ || 18 || <tt>CppClassType</tt>
|-
| KDevPlatform || 20 || <tt>EnumeratorType</tt>
|-
| KDevPlatform || 21 || <tt>EnumerationType</tt>
|-
| C++ || 23 || <tt>CppTemplateParameterType</tt>
|-
| KDevPlatform || 39 || <tt>UnsureType</tt>
|-
| C++ || 42 || <tt>PtrToMemberType</tt>
|-
| PHP || 50 || <tt>IntegralTypeExtended</tt>
|-
| PHP || 51 || <tt>StructureType</tt>
|-
| Python || 59 || <tt>IndexedContainer</tt>
|-
| Python || 60 || <tt>IntegralTypeExtended</tt>
|-
| Python || 61 || <tt>VariableLengthContainer</tt>
|-
| Python || 62 || <tt>HintedType</tt>
|-
| Python || 63 || <tt>UnsureType</tt>
|}

Projects/KDevelop4/DUChainIdentities

2013-01-23T04:26:23Z

Nicolás: Add now-removed Python declaration ID

This is a list of ranges used by various plugins for their Declaration and Type identities.

Please edit this page as appropriate, it's probably not complete like this.

{|class="wikitable"
!Category
!ID
!Use
|-
| KDevPlatform || 1 || <tt>DUChainBase</tt>
|-
| KDevPlatform || 2 || <tt>DUContext</tt>
|-
| KDevPlatform || 4 || <tt>TopDUContext</tt>
|-
| KDevPlatform || 6 || <tt>AliasDeclaration</tt>
|-
| KDevPlatform || 7 || <tt>Declaration</tt>
|-
| KDevPlatform || 9 || <tt>ClassMemberDeclaration</tt>
|-
| KDevPlatform || 10 || <tt>ForwardDeclaration</tt>
|-
| KDevPlatform || 11 || <tt>ParsingEnvironmentFile</tt>
|-
| KDevPlatform || 12 || <tt>FunctionDeclaration</tt>
|-
| KDevPlatform || 13 || <tt>NamespaceAliasDeclaration</tt>
|-
| KDevPlatform || 14 || <tt>ClassFunctionDeclaration</tt>
|-
| KDevPlatform || 15 || <tt>Problem</tt>
|-
| KDevPlatform || 17 || <tt>ClassDeclaration</tt>
|-
| C++ || 18 || <tt>TemplateParameterDeclaration</tt>
|-
| KDevPlatform || 21 || <tt>FunctionDefinition</tt>
|-
| C++ || 52 || <tt>CppDUContext<TopDUContext></tt> (aka <tt>CppNormalDUContext</tt>)
|-
| PHP || 53 || <tt>PhpDUContext<DUContext></tt> (aka <tt>PhpNormalDUContext</tt>)
|-
| C++ || 54 || <tt>CppDUContext<DUContext></tt> (aka <tt>CppTopDUContext</tt>)
|-
| PHP || 55 || <tt>PhpDUContext<TopDUContext></tt> (aka <tt>PhpTopDUContext</tt>)
|-
| C++ || 56 || <tt>SpecialTemplateDeclaration<AliasDeclaration></tt>
|-
| C++ || 57 || <tt>SpecialTemplateDeclaration<Declaration></tt>
|-
| C++ || 59 || <tt>SpecialTemplateDeclaration<ClassMemberDeclaration></tt>
|-
| C++ || 60 || <tt>SpecialTemplateDeclaration<ForwardDeclaration></tt>
|-
| C++ || 62 || <tt>SpecialTemplateDeclaration<FunctionDeclaration></tt>
|-
| C++ || 64 || <tt>SpecialTemplateDeclaration<ClassFunctionDeclaration></tt>
|-
| C++ || 67 || <tt>SpecialTemplateDeclaration<ClassDeclaration></tt>
|-
| C++ || 68 || <tt>SpecialTemplateDeclaration<ClassDeclaration></tt>
|-
| C++ || 71 || <tt>SpecialTemplateDeclaration<FunctionDefinition></tt>
|-
| C++ || 73 || <tt>EnvironmentFile</tt>
|-
| C++ || 74 || <tt>QtFunctionDeclaration</tt>
|-
| C++ || 75 || <tt>QPropertyDeclaration</tt>
|-
| PHP || 80 || <tt><s>ConstantDeclaration</s></tt> (not used anymore)
|-
| PHP || 81 || <tt><s>ClassDeclaration</s></tt> (not used anymore)
|-
| PHP || 83 || <tt>VariableDeclaration</tt>
|-
| PHP || 84 || <tt>ClassMethodDeclaration</tt>
|-
| PHP || 85 || <tt>ClassDeclaration</tt>
|-
| PHP || 86 || <tt>FunctionDeclaration</tt>
|-
| PHP || 87 || <tt>NamespaceDeclaration</tt>
|-
| PHP || 88 || <tt>NamespaceAliasDeclaration</tt>
|-
| XML || 90-99
|-
| Python || 100 || <tt>PythonDUContext<TopDUContext></tt> (aka <tt>PythonTopDUContext</tt>)
|-
| Python || 101 || <tt>PythonDUContext<DUContext></tt> (aka <tt>PythonNormalDUContext</tt>)
|-
| C++ || 124 || <tt>SpecialTemplateDeclaration<QtFunctionDeclaration></tt>
|-
| Python || 125 || <tt>ClassDeclaration</tt>
|-
| Python || 126 || <tt>FunctionDeclaration</tt>
|-
| Python || 127 || <tt><s>ClassFunctionDeclaration</s></tt> (not used anymore)
|}

{|class="wikitable"
|+ Types
!Category
!ID
!Use
|-
| KDevPlatform || 1 || <tt>AbstractType</tt>
|-
| KDevPlatform || 2 || <tt>IntegralType</tt>
|-
| KDevPlatform || 3 || <tt>PointerType</tt>
|-
| KDevPlatform || 4 || <tt>ReferenceType</tt>
|-
| KDevPlatform || 5 || <tt>FunctionType</tt>
|-
| KDevPlatform || 6 || <tt>StructureType</tt>
|-
| KDevPlatform || 7 || <tt>ArrayType</tt>
|-
| KDevPlatform || 8 || <tt>DelayedType</tt>
|-
| KDevPlatform || 9 || <tt>TypeAliasType</tt>
|-
| KDevPlatform || 14 || <tt>ConstantIntegralType</tt>
|-
| C++ || 18 || <tt>CppClassType</tt>
|-
| KDevPlatform || 20 || <tt>EnumeratorType</tt>
|-
| KDevPlatform || 21 || <tt>EnumerationType</tt>
|-
| C++ || 23 || <tt>CppTemplateParameterType</tt>
|-
| KDevPlatform || 39 || <tt>UnsureType</tt>
|-
| C++ || 42 || <tt>PtrToMemberType</tt>
|-
| PHP || 50 || <tt>IntegralTypeExtended</tt>
|-
| PHP || 51 || <tt>StructureType</tt>
|-
| Python || 59 || <tt>IndexedContainer</tt>
|-
| Python || 60 || <tt>IntegralTypeExtended</tt>
|-
| Python || 61 || <tt>VariableLengthContainer</tt>
|-
| Python || 62 || <tt>HintedType</tt>
|-
| Python || 63 || <tt>UnsureType</tt>
|}

Projects/KDevelop4/DUChainIdentities

2013-01-23T04:21:22Z

Nicolás: Added Python IDs

This is a list of ranges used by various plugins for their Declaration and Type identities.

Please edit this page as appropriate, it's probably not complete like this.

{|class="wikitable"
!Category
!ID
!Use
|-
| KDevPlatform || 1 || <tt>DUChainBase</tt>
|-
| KDevPlatform || 2 || <tt>DUContext</tt>
|-
| KDevPlatform || 4 || <tt>TopDUContext</tt>
|-
| KDevPlatform || 6 || <tt>AliasDeclaration</tt>
|-
| KDevPlatform || 7 || <tt>Declaration</tt>
|-
| KDevPlatform || 9 || <tt>ClassMemberDeclaration</tt>
|-
| KDevPlatform || 10 || <tt>ForwardDeclaration</tt>
|-
| KDevPlatform || 11 || <tt>ParsingEnvironmentFile</tt>
|-
| KDevPlatform || 12 || <tt>FunctionDeclaration</tt>
|-
| KDevPlatform || 13 || <tt>NamespaceAliasDeclaration</tt>
|-
| KDevPlatform || 14 || <tt>ClassFunctionDeclaration</tt>
|-
| KDevPlatform || 15 || <tt>Problem</tt>
|-
| KDevPlatform || 17 || <tt>ClassDeclaration</tt>
|-
| C++ || 18 || <tt>TemplateParameterDeclaration</tt>
|-
| KDevPlatform || 21 || <tt>FunctionDefinition</tt>
|-
| C++ || 52 || <tt>CppDUContext<TopDUContext></tt> (aka <tt>CppNormalDUContext</tt>)
|-
| PHP || 53 || <tt>PhpDUContext<DUContext></tt> (aka <tt>PhpNormalDUContext</tt>)
|-
| C++ || 54 || <tt>CppDUContext<DUContext></tt> (aka <tt>CppTopDUContext</tt>)
|-
| PHP || 55 || <tt>PhpDUContext<TopDUContext></tt> (aka <tt>PhpTopDUContext</tt>)
|-
| C++ || 56 || <tt>SpecialTemplateDeclaration<AliasDeclaration></tt>
|-
| C++ || 57 || <tt>SpecialTemplateDeclaration<Declaration></tt>
|-
| C++ || 59 || <tt>SpecialTemplateDeclaration<ClassMemberDeclaration></tt>
|-
| C++ || 60 || <tt>SpecialTemplateDeclaration<ForwardDeclaration></tt>
|-
| C++ || 62 || <tt>SpecialTemplateDeclaration<FunctionDeclaration></tt>
|-
| C++ || 64 || <tt>SpecialTemplateDeclaration<ClassFunctionDeclaration></tt>
|-
| C++ || 67 || <tt>SpecialTemplateDeclaration<ClassDeclaration></tt>
|-
| C++ || 68 || <tt>SpecialTemplateDeclaration<ClassDeclaration></tt>
|-
| C++ || 71 || <tt>SpecialTemplateDeclaration<FunctionDefinition></tt>
|-
| C++ || 73 || <tt>EnvironmentFile</tt>
|-
| C++ || 74 || <tt>QtFunctionDeclaration</tt>
|-
| C++ || 75 || <tt>QPropertyDeclaration</tt>
|-
| PHP || 80 || <tt>ConstantDeclaration</tt> (not used anymore)
|-
| PHP || 81 || <tt>ClassDeclaration</tt> (not used anymore)
|-
| PHP || 83 || <tt>VariableDeclaration</tt>
|-
| PHP || 84 || <tt>ClassMethodDeclaration</tt>
|-
| PHP || 85 || <tt>ClassDeclaration</tt>
|-
| PHP || 86 || <tt>FunctionDeclaration</tt>
|-
| PHP || 87 || <tt>NamespaceDeclaration</tt>
|-
| PHP || 88 || <tt>NamespaceAliasDeclaration</tt>
|-
| XML || 90-99
|-
| Python || 100 || <tt>PythonDUContext<TopDUContext></tt> (aka <tt>PythonTopDUContext</tt>)
|-
| Python || 101 || <tt>PythonDUContext<DUContext></tt> (aka <tt>PythonNormalDUContext</tt>)
|-
| C++ || 124 || <tt>SpecialTemplateDeclaration<QtFunctionDeclaration></tt>
|-
| Python || 125 || <tt>ClassDeclaration</tt>
|-
| Python || 126 || <tt>FunctionDeclaration</tt>
|}

{|class="wikitable"
|+ Types
!Category
!ID
!Use
|-
| KDevPlatform || 1 || <tt>AbstractType</tt>
|-
| KDevPlatform || 2 || <tt>IntegralType</tt>
|-
| KDevPlatform || 3 || <tt>PointerType</tt>
|-
| KDevPlatform || 4 || <tt>ReferenceType</tt>
|-
| KDevPlatform || 5 || <tt>FunctionType</tt>
|-
| KDevPlatform || 6 || <tt>StructureType</tt>
|-
| KDevPlatform || 7 || <tt>ArrayType</tt>
|-
| KDevPlatform || 8 || <tt>DelayedType</tt>
|-
| KDevPlatform || 9 || <tt>TypeAliasType</tt>
|-
| KDevPlatform || 14 || <tt>ConstantIntegralType</tt>
|-
| C++ || 18 || <tt>CppClassType</tt>
|-
| KDevPlatform || 20 || <tt>EnumeratorType</tt>
|-
| KDevPlatform || 21 || <tt>EnumerationType</tt>
|-
| C++ || 23 || <tt>CppTemplateParameterType</tt>
|-
| KDevPlatform || 39 || <tt>UnsureType</tt>
|-
| C++ || 42 || <tt>PtrToMemberType</tt>
|-
| PHP || 50 || <tt>IntegralTypeExtended</tt>
|-
| PHP || 51 || <tt>StructureType</tt>
|-
| Python || 59 || <tt>IndexedContainer</tt>
|-
| Python || 60 || <tt>IntegralTypeExtended</tt>
|-
| Python || 61 || <tt>VariableLengthContainer</tt>
|-
| Python || 62 || <tt>HintedType</tt>
|-
| Python || 63 || <tt>UnsureType</tt>
|}

Projects/KDevelop4/DUChainIdentities

2013-01-23T04:15:09Z

Nicolás: Add PHP contexts, move PHP types to the type table

This is a list of ranges used by various plugins for their Declaration and Type identities.

Please edit this page as appropriate, it's probably not complete like this.

{|class="wikitable"
!Category
!ID
!Use
|-
| KDevPlatform || 1 || <tt>DUChainBase</tt>
|-
| KDevPlatform || 2 || <tt>DUContext</tt>
|-
| KDevPlatform || 4 || <tt>TopDUContext</tt>
|-
| KDevPlatform || 6 || <tt>AliasDeclaration</tt>
|-
| KDevPlatform || 7 || <tt>Declaration</tt>
|-
| KDevPlatform || 9 || <tt>ClassMemberDeclaration</tt>
|-
| KDevPlatform || 10 || <tt>ForwardDeclaration</tt>
|-
| KDevPlatform || 11 || <tt>ParsingEnvironmentFile</tt>
|-
| KDevPlatform || 12 || <tt>FunctionDeclaration</tt>
|-
| KDevPlatform || 13 || <tt>NamespaceAliasDeclaration</tt>
|-
| KDevPlatform || 14 || <tt>ClassFunctionDeclaration</tt>
|-
| KDevPlatform || 15 || <tt>Problem</tt>
|-
| KDevPlatform || 17 || <tt>ClassDeclaration</tt>
|-
| C++ || 18 || <tt>TemplateParameterDeclaration</tt>
|-
| KDevPlatform || 21 || <tt>FunctionDefinition</tt>
|-
| C++ || 52 || <tt>CppDUContext<TopDUContext></tt> (aka <tt>CppNormalDUContext</tt>)
|-
| PHP || 53 || <tt>PhpDUContext<DUContext></tt> (aka <tt>PhpNormalDUContext</tt>)
|-
| C++ || 54 || <tt>CppDUContext<DUContext></tt> (aka <tt>CppTopDUContext</tt>)
|-
| PHP || 55 || <tt>PhpDUContext<TopDUContext></tt> (aka <tt>PhpTopDUContext</tt>)
|-
| C++ || 56 || <tt>SpecialTemplateDeclaration<AliasDeclaration></tt>
|-
| C++ || 57 || <tt>SpecialTemplateDeclaration<Declaration></tt>
|-
| C++ || 59 || <tt>SpecialTemplateDeclaration<ClassMemberDeclaration></tt>
|-
| C++ || 60 || <tt>SpecialTemplateDeclaration<ForwardDeclaration></tt>
|-
| C++ || 62 || <tt>SpecialTemplateDeclaration<FunctionDeclaration></tt>
|-
| C++ || 64 || <tt>SpecialTemplateDeclaration<ClassFunctionDeclaration></tt>
|-
| C++ || 67 || <tt>SpecialTemplateDeclaration<ClassDeclaration></tt>
|-
| C++ || 68 || <tt>SpecialTemplateDeclaration<ClassDeclaration></tt>
|-
| C++ || 71 || <tt>SpecialTemplateDeclaration<FunctionDefinition></tt>
|-
| C++ || 73 || <tt>EnvironmentFile</tt>
|-
| C++ || 74 || <tt>QtFunctionDeclaration</tt>
|-
| C++ || 75 || <tt>QPropertyDeclaration</tt>
|-
| PHP || 80 || <tt>ConstantDeclaration</tt> (not used anymore)
|-
| PHP || 81 || <tt>ClassDeclaration</tt> (not used anymore)
|-
| PHP || 83 || <tt>VariableDeclaration</tt>
|-
| PHP || 84 || <tt>ClassMethodDeclaration</tt>
|-
| PHP || 85 || <tt>ClassDeclaration</tt>
|-
| PHP || 86 || <tt>FunctionDeclaration</tt>
|-
| PHP || 87 || <tt>NamespaceDeclaration</tt>
|-
| PHP || 88 || <tt>NamespaceAliasDeclaration</tt>
|-
| XML || 90-99
|-
| C++ || 124 || <tt>SpecialTemplateDeclaration<QtFunctionDeclaration></tt>
|}

{|class="wikitable"
|+ Types
!Category
!ID
!Use
|-
| KDevPlatform || 1 || <tt>AbstractType</tt>
|-
| KDevPlatform || 2 || <tt>IntegralType</tt>
|-
| KDevPlatform || 3 || <tt>PointerType</tt>
|-
| KDevPlatform || 4 || <tt>ReferenceType</tt>
|-
| KDevPlatform || 5 || <tt>FunctionType</tt>
|-
| KDevPlatform || 6 || <tt>StructureType</tt>
|-
| KDevPlatform || 7 || <tt>ArrayType</tt>
|-
| KDevPlatform || 8 || <tt>DelayedType</tt>
|-
| KDevPlatform || 9 || <tt>TypeAliasType</tt>
|-
| KDevPlatform || 14 || <tt>ConstantIntegralType</tt>
|-
| C++ || 18 || <tt>CppClassType</tt>
|-
| KDevPlatform || 20 || <tt>EnumeratorType</tt>
|-
| KDevPlatform || 21 || <tt>EnumerationType</tt>
|-
| C++ || 23 || <tt>CppTemplateParameterType</tt>
|-
| KDevPlatform || 39 || <tt>UnsureType</tt>
|-
| C++ || 42 || <tt>PtrToMemberType</tt>
|-
| PHP || 50 || <tt>IntegralTypeExtended</tt>
|-
| PHP || 51 || <tt>StructureType</tt>
|}

Projects/KDevelop4/DUChainIdentities

2013-01-23T04:10:35Z

Nicolás: Add KDevPlatform type IDs

This is a list of ranges used by various plugins for their Declaration and Type identities.

Please edit this page as appropriate, it's probably not complete like this.

{|class="wikitable"
!Category
!ID
!Use
|-
| KDevPlatform || 1 || <tt>DUChainBase</tt>
|-
| KDevPlatform || 2 || <tt>DUContext</tt>
|-
| KDevPlatform || 4 || <tt>TopDUContext</tt>
|-
| KDevPlatform || 6 || <tt>AliasDeclaration</tt>
|-
| KDevPlatform || 7 || <tt>Declaration</tt>
|-
| KDevPlatform || 9 || <tt>ClassMemberDeclaration</tt>
|-
| KDevPlatform || 10 || <tt>ForwardDeclaration</tt>
|-
| KDevPlatform || 11 || <tt>ParsingEnvironmentFile</tt>
|-
| KDevPlatform || 12 || <tt>FunctionDeclaration</tt>
|-
| KDevPlatform || 13 || <tt>NamespaceAliasDeclaration</tt>
|-
| KDevPlatform || 14 || <tt>ClassFunctionDeclaration</tt>
|-
| KDevPlatform || 15 || <tt>Problem</tt>
|-
| KDevPlatform || 17 || <tt>ClassDeclaration</tt>
|-
| C++ || 18 || <tt>TemplateParameterDeclaration</tt>
|-
| KDevPlatform || 21 || <tt>FunctionDefinition</tt>
|-
| PHP || 50 || <tt>IntegralTypeExtended</tt>
|-
| PHP || 51 || <tt>StructureType</tt>
|-
| C++ || 52 || <tt>CppDUContext<TopDUContext></tt> (aka <tt>CppNormalDUContext</tt>)
|-
| C++ || 54 || <tt>CppDUContext<DUContext></tt> (aka <tt>CppTopDUContext</tt>)
|-
| C++ || 56 || <tt>SpecialTemplateDeclaration<AliasDeclaration></tt>
|-
| C++ || 57 || <tt>SpecialTemplateDeclaration<Declaration></tt>
|-
| C++ || 59 || <tt>SpecialTemplateDeclaration<ClassMemberDeclaration></tt>
|-
| C++ || 60 || <tt>SpecialTemplateDeclaration<ForwardDeclaration></tt>
|-
| C++ || 62 || <tt>SpecialTemplateDeclaration<FunctionDeclaration></tt>
|-
| C++ || 64 || <tt>SpecialTemplateDeclaration<ClassFunctionDeclaration></tt>
|-
| C++ || 67 || <tt>SpecialTemplateDeclaration<ClassDeclaration></tt>
|-
| C++ || 68 || <tt>SpecialTemplateDeclaration<ClassDeclaration></tt>
|-
| C++ || 71 || <tt>SpecialTemplateDeclaration<FunctionDefinition></tt>
|-
| C++ || 73 || <tt>EnvironmentFile</tt>
|-
| C++ || 74 || <tt>QtFunctionDeclaration</tt>
|-
| C++ || 75 || <tt>QPropertyDeclaration</tt>
|-
| PHP || 80 || <tt>ConstantDeclaration</tt> (not used anymore)
|-
| PHP || 81 || <tt>ClassDeclaration</tt> (not used anymore)
|-
| PHP || 83 || <tt>VariableDeclaration</tt>
|-
| PHP || 84 || <tt>ClassMethodDeclaration</tt>
|-
| PHP || 85 || <tt>ClassDeclaration</tt>
|-
| PHP || 86 || <tt>FunctionDeclaration</tt>
|-
| PHP || 87 || <tt>NamespaceDeclaration</tt>
|-
| PHP || 88 || <tt>NamespaceAliasDeclaration</tt>
|-
| XML || 90-99
|-
| C++ || 124 || <tt>SpecialTemplateDeclaration<QtFunctionDeclaration></tt>
|}

{|class="wikitable"
|+ Types
!Category
!ID
!Use
|-
| KDevPlatform || 1 || <tt>AbstractType</tt>
|-
| KDevPlatform || 2 || <tt>IntegralType</tt>
|-
| KDevPlatform || 3 || <tt>PointerType</tt>
|-
| KDevPlatform || 4 || <tt>ReferenceType</tt>
|-
| KDevPlatform || 5 || <tt>FunctionType</tt>
|-
| KDevPlatform || 6 || <tt>StructureType</tt>
|-
| KDevPlatform || 7 || <tt>ArrayType</tt>
|-
| KDevPlatform || 8 || <tt>DelayedType</tt>
|-
| KDevPlatform || 9 || <tt>TypeAliasType</tt>
|-
| KDevPlatform || 14 || <tt>ConstantIntegralType</tt>
|-
| C++ || 18 || <tt>CppClassType</tt>
|-
| KDevPlatform || 20 || <tt>EnumeratorType</tt>
|-
| KDevPlatform || 21 || <tt>EnumerationType</tt>
|-
| C++ || 23 || <tt>CppTemplateParameterType</tt>
|-
| KDevPlatform || 39 || <tt>UnsureType</tt>
|-
| C++ || 42 || <tt>PtrToMemberType</tt>
|}

Projects/KDevelop4/DUChainIdentities

2013-01-23T04:05:05Z

Nicolás: Add C++ IDs. Stop using spanned rows; it's hard to represent the data with that. I may restore them later.

Projects/KDevelop4/DUChainIdentities

2013-01-23T03:29:59Z

Nicolás: Add KDevPlatform IDs

Projects/KDevelop4/DUChainIdentities

2013-01-23T03:04:37Z

Nicolás: Add more (all?) PHP identity types

This is a list of ranges used by various plugins for their Declaration and Type identities.

Please edit this page as appropriate, it's probably not complete like this.

{|class="wikitable"
!Category
!ID
|-
| C++ / KDevPlatform || 0-39
|-
| Java || 30-40
|-
| C++ || 40-49
|-
| rowspan="3" | PHP
| 50 || <tt>IntegralTypeExtended</tt>
|-
| 51 || <tt>StructureType</tt>
|-
| 52-59 || not used yet
|-
| Ruby, Python || 60-69
|-
| C++ || 70-79
|-
| rowspan="10" | PHP
| 80 || <tt>ConstantDeclaration</tt> (not used anymore)
|-
| 81 || <tt>ClassDeclaration</tt> (not used anymore)
|-
| 82 || apparently never used
|-
| 83 || <tt>VariableDeclaration</tt>
|-
| 84 || <tt>ClassMethodDeclaration</tt>
|-
| 85 || <tt>ClassDeclaration</tt>
|-
| 86 || <tt>FunctionDeclaration</tt>
|-
| 87 || <tt>NamespaceDeclaration</tt>
|-
| 88 || <tt>NamespaceAliasDeclaration</tt>
|-
| 89 || unused
|-
| XML || 90-99
|}

Projects/KDevelop4/DUChainIdentities

2013-01-23T00:40:39Z

Nicolás: Added more PHP IDs

This is a list of ranges used by various plugins for their Declaration and Type identities.

Please edit this page as appropriate, it's probably not complete like this.

{|class="wikitable"
!Category
!ID
|-
| C++ / KDevPlatform || 0-39
|-
| Java || 30-40
|-
| C++ || 40-49
|-
| rowspan="3" | PHP
| 50 || IntegralTypeExtended
|-
| 51 || StructureType
|-
| 52-59
|-
| Ruby, Python || 60-69
|-
| C++ || 70-79
|-
| rowspan="4" | PHP
| 80-82
|-
| 83 || VariableDeclaration
|-
| 84 || ClassMethodDeclaration
|-
| 85-89
|-
| XML || 90-99
|}

Projects/KDevelop4/DUChainIdentities

2013-01-23T00:37:25Z

Nicolás: Add some specific PHP numbers

This is a list of ranges used by various plugins for their Declaration and Type identities.

Please edit this page as appropriate, it's probably not complete like this.

{|class="wikitable"
!Category
!ID
|-
| C++ / KDevPlatform || 0-39
|-
| Java || 30-40
|-
| C++ || 40-49
|-
| rowspan="3" | PHP
| 50 || IntegralTypeExtended
|-
| 51 || StructureType
|-
| 52-59
|-
| Ruby, Python || 60-69
|-
| C++ || 70-79
|-
| PHP || 80-89
|-
| XML || 90-99
|}

Projects/KDevelop4/DUChainIdentities

2013-01-23T00:31:40Z

Nicolás: Swap columns

This is a list of ranges used by various plugins for their Declaration and Type identities.

Please edit this page as appropriate, it's probably not complete like this.

{|class="wikitable"
!Category
!ID
|-
| C++ / KDevPlatform || 0-39
|-
| Java || 30-40
|-
| C++ || 40-49
|-
| PHP || 50-59
|-
| Ruby, Python || 60-69
|-
| C++ || 70-79
|-
| PHP || 80-89
|-
| XML || 90-99
|}

Projects/KDevelop4/DUChainIdentities

2013-01-23T00:29:46Z

Nicolás: Format as an actual table

This is a list of ranges used by various plugins for their Declaration and Type identities.

Please edit this page as appropriate, it's probably not complete like this.

{|class="wikitable"
!Range
!Use
|-
|0-39 || C++ / KDevPlatform
|-
|30-40 || Java
|-
|40-49 || C++
|-
|50-59 || PHP
|-
|60-69 || Ruby, Python
|-
|70-79 || C++
|-
|80-89 || PHP
|-
|90-99 || XML
|}

Getting Started/Sources/Subversion

2012-12-29T18:08:22Z

Nicolás:

{{TutorialBrowser|
series=Getting Started|
name=Using Subversion With KDE|
reading=[[Contribute/Send Patches|Contributing/Sending Patches]]|
reading=[http://svnbook.red-bean.com/ Version Control with Subversion]|
}}

{{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 is a quick KDE-specific introduction for using Subversion to access files and software in KDE's repositories. For comprehensive coverage of Subversion we recommend reading the book "[http://svnbook.red-bean.com/ Version Control with Subversion]".

== Getting started ==

In order to use the KDE Subversion repository, you will need a Subversion client program.

If you only need SVN for checking out the sources (read-only), use the protocol: "svn" at the server: "anonsvn.kde.org".

So for example, instead of what you see throughout this tutorial, your paths would be similar to this: svn://anonsvn.kde.org/home/kde/trunk/KDE/kdevelop

Note: Wherever it mentions "yourname@", http, https, or passwords, you should ignore those and use what is mentioned. None of that stuff is needed for the anonymous server.

If you would like to commit changes to the repository, you will need an SVN account, which is obtainable here: [[Get a SVN Account|get an SVN Account]]. 

----

'''Installing Subversion:''' instructions on installing the client are not presented here. Refer to your system installation instructions to find out how you can install Subversion. You will need version 1.1 at least . If you are compiling from sources and want to access the KDE repository by https (and not by svn+ssh), you will need SSL and ZLIB support, so you will need the <tt>--with-ssl --with-zlib</tt> options.

Alternatively, you can install one of the many graphical clients out there (for example, kdesvn, albeit unofficial). This tutorial is intended for people using the <tt>svn</tt> program only, referring to tasks accomplished with the usual <tt>cvs</tt> program.

'''Getting an account:''' if you have had a CVS account before, it has been migrated to the new Subversion client.

== The KDE repository structure ==

svn.kde.org/home/kde

That's the address of the KDE Subversion repository. The repository is served by HTTPS or SVN+SSH protocol, which means your password is secure against third-party eavesdropping.

The SSL certificate md5 fingerprint for the repositories:

F6BF EDE2 D016 D1B2 4F18 742E 2C8F B7EF

The SSL certificate sha1 fingerprint for the repositories:

e1:e6:41:96:3c:eb:ae:78:e2:73:0d:a2:32:2f:6b:21:13:bf:3d:0f

For people using svn+ssh, here's the fingerprint of the server's RSA key:

1e:89:fa:0d:c3:11:a4:81:36:84:b6:f2:6b:f0:5b:ad

The repository is organised in main directories:

#/branches
#/tags
#/trunk

You can explore the repository structure at [http://websvn.kde.org/ http://websvn.kde.org/]

 

=== The top-level directory /trunk ===

The <tt>/trunk</tt> top-level subdirectory is where the main development for KDE occurs. What you will find here is what will become the next KDE release and its associated programs. Here you will also find the <tt>www</tt> module, which contains webpages for KDE's site and related ones.

<tt>/trunk</tt> is further subdivided into these sub-directories:

*<tt>KDE/</tt> KDE itself, what will become the next public release. It contains the following modules:
**'''kdelibs''' - KDE basic libraries, used by all KDE programs
**'''kdebase''' - KDE base programs, like the KDE Control Center, Kicker (the panel) and Konqueror (the web browser)
**'''kdeaccessibility''' - Accessibility files
**'''kdeadmin''' - KDE Administration applications
**'''kdeartwork''' - Images, themes, sounds and other art files
**'''kdebindings''' - Bindings for languages other than C++
**'''kdeedu''' - KDE Educational applications
**'''kdegames''' - KDE Games
**'''kdegraphics''' - KDE Graphical applications
**'''kdemultimedia''' - KDE Multimedia applications
**'''kdenetwork''' - KDE Networking applications
**'''kdepim''' - KDE Personal Information Management applications
**'''kdepimlibs''' - Libraries used by KDE-PIM applications.
**'''kdesdk''' - KDE Software Development Kit applications
**'''kdetoys''' - KDE toy applications
**'''kdeutils''' - KDE General utilities
**'''kdewebdev''' - KDE Web development applications
*<tt>kde-common</tt>

:Common admin/ directory

*<tt>bugs/</tt>

:[http://bugs.kde.org/ Bugzilla] files

*<tt>developer.kde.org/</tt>

:The content of developer.kde.org

*<tt>extragear/</tt>

:KDE programs outside the main KDE releases.

*<tt>kdereview/</tt>

:Temporary home for KDE applications that are believed to have reached release-quality. From here, once all major issues are resolved, applications are moved either to <tt>/trunk/KDE/</tt> or to <tt>/trunk/extragear/</tt>

*<tt>kdesupport/</tt>

:Supporting applications and libraries for KDE

*<tt>koffice/</tt> The KDE Office suite, containing the programs:
**'''karbon'''
**'''kchart'''
**'''kexi'''
**'''kformula'''
**'''kivio'''
**'''koshell'''
**'''kplato'''
**'''kpresenter'''
**'''krita'''
**'''kspread'''
**'''kword'''
*<tt>konstruct/</tt>

:Konstruct, the KDE build program

*<tt>l10n-kde3/</tt>

:Translations for the "unstable" modules of KDE 3 (extragear, playground)

*<tt>l10n-kde4/</tt>

:Translations for KDE 4

*<tt>playground/</tt>

:The KDE playground: applications being developed, but not having yet reached release-quality.

*<tt>qt-copy/</tt>

:The convenience copy of [http://www.trolltech.com/ Trolltech's] Qt library, which KDE is based upon. Remember, this is deprecated, you should be using the git repository, kde-qt instead. Qt-copy is at version 4.5, yet trunk '''requires '''

*<tt>tests/</tt>

:khtml, KOffice and ksvg testcases

*<tt>valgrind/</tt>

:The Valgrind application, which is hosted on the KDE repository, but that is not part of KDE itself. Note that newer versions of Valgrind are developed on their own repository. The KDE Valgrind modules only holds up to Valgrind 2.4.

*<tt>www/</tt>

:Webpages for the KDE site (and related sites). Write access to this directory is restricted.

=== The top-level directory <tt>/tags</tt> ===

This directory contains the official releases of the programs maintained and developed in the KDE repository. Each individual application has a subdirectory here. Inside it, you will find the release numbers.

For instance, the KDE 3.4.0 code can be found under <tt>/tags/KDE/3.4.0/</tt>.

=== The top-level directory <tt>/branches</tt> ===

This directory contains the branch versions of the applications after a major release.

Most KDE applications adhere to the philosphy that new features (as well as new user-visible strings) are added only to the next release cycle — the one that lives in <tt>/trunk/</tt>. However, bugfixes are applied to all applications, even after release.

In order to do that, a branch is created at the moment of the release, indicating the state of the files at that time. Bugfixes are then checked in to those files. Those branches are the ones in <tt>/branches/</tt>.

For instance, the KDE 3.4.x branch can be found under <tt>/branches/KDE/3.4/</tt>

The subdirectories you will find inside <tt>/branches</tt> are the application subdirs, like <tt>akregator/</tt>, <tt>amarok/</tt>, <tt>arts/</tt>, <tt>k3b/</tt>, etc. You will also find a <tt>KDE/</tt> subdir, containing the official KDE releases since time immemorial.

One special subdir is found in <tt>/branches</tt>: <tt>work/</tt>. This subdir contains the so-called "work branches", that is, branches containing features being worked on, sometimes highly experimental. Multi-application work branches always are checked in to <tt>/branches/work/</tt>, but single-application branches may be found in each application's subdir. That is a decision left to the developers.

 

== Checking out and updating ==

=== Checking out ===

In order to check out something with Subversion, you use the <tt>checkout</tt> subcommand.

'''WARNING:''' If you checkout trunk/KDE/ or branches/KDE/foo/ you will download complete kde-i18n!

Suppose you wanted to check out only kdeedu from the KDE repository. You would do:

Subversion users currently using ssh access should use protocol svn+ssh while subversion users currently using password access should use protocol https in the following:

svn checkout --username=<username> <protocol>://svn.kde.org/home/kde/trunk/KDE/kdeedu

For checking out kdevelop from extragear you would do:

svn checkout --username=<username> <protocol>://svn.kde.org/home/kde/trunk/extragear/sdk/kdevelop

Note that you may wish to use the following if the above doesn't work:

svn checkout <protocol>://<username>@svn.kde.org/home/kde/trunk/extragear/sdk/kdevelop

=== Updating ===

In order to update, you use the <tt>update</tt> subcommand.

You change into your checked out copy (for those new to this whole process, the checked out copy should be in your Home folder) and issue a <tt>svn update</tt> (or, shorter, <tt>svn up</tt>) command.

== Knowing the status of a file ==

To know which local files you had modified, you have to do

svn status

and look at the files with '''M''' (for modified).

== Committing to the repository ==

Committing to the Subversion repository is accomplished with the <tt>commit</tt> (<tt>ci</tt> for short) subcommands:

svn commit
# or
svn ci
# or
svn ci filename.cpp

This way, <tt>svn</tt> will launch the editor specified in <tt>$SVN_EDITOR</tt> for you to compose the commit message. If you prefer, you can give <tt>svn</tt> the -m option with your full message:

svn ci -m "Updating protocol to conform to HTTP/1.1"

== Ignoring files ==

Subversion stores ignored files per directory. To edit the ignored files of the directory you are currently in, do

svn propedit svn:ignore .

that will launch your editor, write there the names of the files you want to ignore, one file per line. Once you are done, do a commit so the ignored list file gets updated on the server.

A lot of files were ignored in CVS with help from global ignore list which is not supported yet by SVN. You can wait for svn 1.3 or you need to add the ignore list to the [miscellany] group in your {{path|~/.subversion/config}} (all in one line):

global-ignores = *.o *.lo *.la .*.rej *.rej .*~ *~ .#* #*# .DS_Store *.moc
*.moc.cc *.moc.cpp config.log config.status config.cache *.gmo .deps .libs
SunWS_cache *.lo *.la *.rpo *.la.closure *_la_closure.cpp *_la_closure.cc
*_la_closure.cxx *.all_cc.cc *.all_cpp.cpp *.all_C.C *.all_cxx.cxx
*_meta_unload.cc *_meta_unload.h *_meta_unload.cpp *_meta_unload.C
*_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in Makefile.calls.in
Makefile.rules Makefile.calls autom4te.cache *.kidl

== Working with multiple revisions and branches ==

Unlike CVS, Subversion doesn't generate a revision number for each file modified. Instead, the full repository is versioned, as a whole. This way, a given revision number represents the state the repository was on a given date. In other words, a revision number is like a timestamp (in fact, the Subversion server uses this fact to search for dates in the repository faster).

So, for instance, when you check out the KDE repository, Subversion will tell you the following:

Updated to revision 403821.

This means that the latest revision available at the time of the operation was 403821. If you make a modification and commit, Subversion will update the server-side revision and will inform you of it. Like CVS, only the committed files will be updated: you will need run <tt>cvs up</tt> to update the rest of the files.

If you want to retrieve a specific revision of a file, you can use the <tt>-r</tt> switch. Besides the revision number itself, -r accepts a number of other possibilities:

*The revision number: for example, use -r 403819 to retrieve that version
*'''BASE''': the revision you updated to
*'''COMMITTED''': the revision a file was last modified, before BASE
*'''PREV''': the revision of the previous commit to the file before COMMITTED
*'''HEAD''': the most recent revision available in the server
*'''{ date }''': between curly brackets, you can specify a date for searching the closest revisions

The following illustrates the evolution of the keywords:

#You run <tt>svn up</tt> to update to the latest available revision. Suppose Subversion tells you it updated to revision 403821. This means that HEAD and BASE are 403821.
#You modify file README and commit it. Suppose Subversion tells you it committed revision 403822. This means HEAD, BASE and COMMITTED are 403822.
#You modify the file again and commit it. Now PREV is 403822, but HEAD, BASE and COMMITTED are updated to a new value (suppose it's 403823).
#Now someone else modifies the repository, and you update your working copy. If Subversion tells you it updated to 403824, this means now HEAD and BASE are moved to 403824 (but PREV and COMMITTED stay the same)
#If someone modifies the README file now, HEAD is moved. The other keywords stay the same for you, until you update. At this time, we will have HEAD = 403825 (the latest available revision), BASE = 403824 (the revision you last updated to), COMMITTED = 403823 (the revision of the latest change to the file when you last updated) and PREV = 403822 (the revision of the change before COMMITTED)

Those keywords are useful to retrieve logs and diffs for commits to the repository.

If you want to see the difference between your working copy and BASE, you can run:

svn diff

This is a very fast operation, since Subversion keeps a local copy of BASE. It doesn't need a network connection to accomplish this operation.

If you want to see the difference between your local copy and the latest available on the server, you will run:

svn diff -r HEAD

If you want to see what has changed in the repository since you've last updated, you can use:

svn diff -r BASE:HEAD

If you want to see the last change to a file before BASE, you can use:

svn diff -r PREV:BASE
# or
svn diff -r PREV:COMMITTED

That is also valid for the <tt>svn log</tt> command.

== Linking in subdirectories from other places ==

It can happen you would like to include a copy of a subdirectory from another place, but just for convenience, not for developing the code in there. Of course it should be updated automatically whenever the original changes. Subversion can help you. You need to edit the property <tt>svn:external</tt> of the directory the subdirectory should be added to. So for the current directory you use

svn propedit svn:externals .

and then enter lines of the form

libkhalkhi svn://anonsvn.kde.org/home/kde/trunk/playground/pim/khalkhi

Updating will now fetch <tt>/trunk/playground/pim/khalkhi</tt> into the subdirectoy <tt>libkhalkhi</tt>.

{{warning|Beware that you cannot commit changes you did to the local copy of the external subdirectory, it is just a readonly copy.}}

You use <tt>svn://anonsvn.kde.org</tt> and not another protocol, because <tt>anonsvn.kde.org</tt> is accessible to everyone. Using <tt>https:</tt> or <tt>svn+ssh:</tt> would only work for users of that protocol. There are still some small disadvantage with <tt>anonsvn.kde.org</tt>: It is not always in synchronization with <tt>svn.kde.org</tt>, so updates in the original branch may take a while to appear on <tt>anonsvn.kde.org</tt>. And some strict firewalls are blocking the <tt>svn:</tt> protocol.

A special case in KDE 3 is the subdirectory <tt>admin</tt>, containing the KDE 3 build utilities. It is linked in to the top directory in all modules, and maintained in <tt>/branches/KDE/3.5/kde-common</tt>. For <tt>admin</tt> the KDE subversion server is configured to allow readonly access for everyone, so if you see

admin https://svn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin

there is no need to change this.

== Further Links ==

*[[Development/Tools/svnmerge.py|Merge tracking with svnmerge.py]]

= Old Getting_started/Sources/Anonymous SVN Page =

== Abstract ==

For those of us that like to stay on the "bleeding edge" there's an easy way to keep a local copy of the KDE sources up-to-date — anonymous SVN.

Alternatively, install [[Getting_Started/Distribution_Packages|KDE SVN packages from your distribution]].

== Anonymous SVN ==

=== Setup Subversion ===

First, install the subversion (svn) binary if it isn't already on your computer. Your operating system should have a package for it. Alternatively you can download and compile it yourself via the [http://subversion.tigris.org/project_packages.html svn project download page]. Please read the [[Getting_Started/Sources/Using_Subversion_with_KDE|KDE Subversion tutorial]] if you are interested in how to use Subversion.

=== Checkout KDE TRUNK ===

'''/trunk/''' is where the Qt4-based KDE 4 is being developed. The following is the minimal set of modules you will need to check out to build KDE and KDE software:

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase

You also need to checkout KDESupport:

svn co svn://anonsvn.kde.org/home/kde/trunk/kdesupport

{{tip|If your firewall doesn't allow access to arbitrary ports, substitute '''svn://anonsvn.kde.org/''' with '''svn://anonsvn4.kde.org:443/''' above.}}

{{tip|The kdebase module has an external dependency, using svn:externals. The problem is, at this time, the externals property is set with an absolute path, pointing to anonsvn. For those using behind a firewall, this is a problem. You can change the property for your workspace, using two commands:
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|cs]] KDE
svn propset svn:externals "lib svn://websvn.kde.org:443/home/kde/trunk/KDE/kdebase/runtime/kstyles/oxygen/lib" kdebase/workspace/kwin/clients/oxygen
svn propset svn:externals "lib svn://websvn.kde.org:443/home/kde/trunk/KDE/kdebase/runtime/kstyles/oxygen/lib" kdebase/workspace/kwin/clients/ozone
This way the external property will look for the additional files in the websvn repository. There are also kdenetwork/kget/transfer-plugins/bittorrent and kdebase/workspace/kwin/clients/ozone that use svn:externals get the url with svn propget svn:externals PATH and replace anonsvn.kde.org with websvn.kde.org:443 here too.}}

'''qt-copy''' is a copy of the latest stable [http://www.trolltech.com Qt] release which works with KDE, put into SVN for convenience. It also contains patches by KDE developers that haven't found their way to Qt yet. They are recommended for those working with KDE from '''trunk'''. Instructions on how to get and configure it can be found [[Getting_Started/Build/Qt |here]].

{{tip| It is recommended to use kde-qt.git instead of qt-copy.

git clone git://gitorious.org/+kde-developers/qt/kde-qt.git qt-kde

}}

If you wish to have a complete copy of KDE TRUNK, you can simply check out the entire source tree with one command:

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE

{{note|It is smarter to first use [http://websvn.kde.org/trunk/KDE The KDE Source Repository Web Viewer]. Use it to choose which modules to download. This way KDE will be quicker to install and try out.}}

If you want additional software packages you can check out the following modules within '''trunk/''' as well:

koffice
extragear
playground
kdereview

So, for example, if you want to check out koffice trunk, you can use:

svn co svn://anonsvn.kde.org/home/kde/trunk/koffice

=== Checking out trunk using snapshots ===

If you are checking out modules from '''trunk/''' you may be able to save time by using snapshots. Using Subversion trunk snapshots is described at [[../Snapshots|the Subversion snapshots tutorial page]].

=== Checking out KDE 3 instead ===

If you want to track KDE 3 rather than the bleeding edge, you may retrieve the KDE 3.5 sources using:

svn co svn://anonsvn.kde.org/home/kde/branches/arts/1.5/arts
svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/

And if you want the matching qt-copy:
svn co svn://anonsvn.kde.org/home/kde/branches/qt/3.3/qt-copy

=== Checking out specific releases ===

KDE modules are also tagged at each release so that it is possible to get a specific release of KDE. Most KDE modules have a tag name in the format '''tags/KDE/X.Y.Z''' (where X, Y and Z represent the exact version). The arts module (only needed for KDE 2 and KDE 3) has a different format of tag name, '''tags/arts/X.Y.Z'''. For instance to get kdelibs as it was shipped in KDE 3.5.0, do:

svn co svn://anonsvn.kde.org/home/kde/tags/KDE/3.5.0/kdelibs/

If you then want to update this checkout to KDE 3.5.5, use this command:

svn switch svn://anonsvn.kde.org/home/kde/tags/KDE/3.5.5/kdelibs

{{tip|If you used a '''/branch/''' or '''/trunk/''' path, then there is no need to switch, just run '''svn update'''.}}

=== Checking out translations ===
If you are looking for translations and other localizations, check out the appropriate language from the appropriate module: [http://websvn.kde.org/trunk/l10n-kde4 l10n-kde4] (KDE4) or [http://websvn.kde.org/trunk/l10n-kde3 l10n-kde3] (KDE3).

{{Warning|The l10n module is ''extremely'' large. Be sure you have lots of time and disk space on hand before checking out the entire l10n module. Most people only check out specific language subdirectories rather than the entire l10n module.}}

You are now ready to start building KDE! Visit [[Getting_Started/Build|this page]] for instructions on building trunk or [[Getting_Started/Build/Stable_Version|this page]] for instruction on compiling the last stable release.

=== Checkout from behind a proxy ===

If the tip above didn't help you, and you've realized that the only way to go seems to be with http://anonsvn.kde.org/.. , then you will have to jump through a few hoops to get an svn checkout. Since http:// access is open only to developers, you will have to use svn://. Transconnect is a small piece of software that can tunnel all the traffic through your friendly neigbourhood proxy server. Get the transconnect sources from http://transconnect.sourceforge.net/ , compile it, and edit ~/.tconn/tconn.conf to point to your proxy server. Export the LD_PRELOAD variable as per the README from transconnect, and you're set to go.

== Also of interest ==
* Visit http://websvn.kde.org/ to browse the source code online.
* anonsvn.kde.org is a round robin DNS entry, which will resolve to one out of several anonsvn mirrors. The DNS setup is maintained by [mailto:sysadmin@kde.org the KDE sysadmins]. However, it might be desireable to choose a local mirror explicitely. Some mirrors are listed below, sorted by performance:
** kde.mneisen.org is located near Nuernberg, Germany, maintained by [mailto:martin.eisenhardt@mneisen.org Martin Eisenhardt]
** www.englishbreakfastnetwork.org also hosts an anonymous SVN mirror, at the University of Nijmegen, Netherlands. Maintained by [mailto:groot@kde.org Adriaan de Groot]

* There are also aliases anonsvn1.kde.org, anonsvn2.kde.org and anonsvn3.kde.org which point to the mirrors used in the DNS round robin (the above two plus another mneisen.org mirror). If you experience trouble because one mirror is broken, you can always select a specific mirror using either the fullnames above or simply anonsvn1, 2, or 3.

: Be careful when switching between mirrors. SVN remembers the server in the working copy, so to switch you have to run
svn switch --relocate svn://anonsvn.kde.org/ svn://kde.mneisen.org/
: in all your checkouts.
If you're interested in setting up a svn mirror, please contact [mailto:sysadmin@kde.org the KDE sysadmins].

[[Category:Build KDE]]

Getting Started/Sources/Subversion

2012-12-29T18:05:21Z

Nicolás: Remove Abstract heading (move contents to intro section). Move warning box below tutorial browser.

{{TutorialBrowser|
series=Getting Started|
name=Using Subversion With KDE|
reading=[[Contribute/Send Patches|Contributing/Sending Patches]]|
reading=[http://svnbook.red-bean.com/ Version Control with Subversion]|
}}

{{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 is a quick KDE-specific introduction for using subversion to access files and software in KDE's repositories. For comprehensive coverage of Subversion we recommend reading the book "[http://svnbook.red-bean.com/ Version Control with Subversion]".

== Getting started ==

In order to use the KDE Subversion repository, you will need a Subversion client program.

If you only need SVN for checking out the sources (read-only), use the protocol: "svn" at the server: "anonsvn.kde.org".

So for example, instead of what you see throughout this tutorial, your paths would show a similarity to this: svn://anonsvn.kde.org/home/kde/trunk/KDE/kdevelop

Note: Wherever it mentions "yourname@", http, https, or passwords, you should ignore those and use what is mentioned. None of that stuff is needed for the anonymous server.

If you would like to commit changes to the repository, you will need an SVN account, which is obtainable here: [http://techbase.kde.org/Contribute/Get_a_SVN_Account get an SVN Account]. 

----

'''Installing Subversion:''' instructions on installing the client are not presented here. Refer to your system installation instructions to find out how you can install Subversion. You will need version 1.1 at least. If you are compiling from sources and want to access the KDE repository by https (and not by svn+ssh), you will need SSL and ZLIB support, so you will need the <tt>--with-ssl --with-zlib</tt> options.

Alternatively, you can install one of the many graphical clients out there(for example, kdesvn, albeit unofficial). This tutorial is intended for people using the <tt>svn</tt> program only, referring to tasks accomplished with the usual <tt>cvs</tt> program.

'''Getting an account:''' if you have had a CVS account before, it has been migrated to the new Subversion client.

== The KDE repository structure ==

svn.kde.org/home/kde

That's the address of the KDE Subversion repository. The repository is served by HTTPS or SVN+SSH protocol, which means your password is secure against third-party eavesdropping.

The SSL certificate md5 fingerprint for the repositories:

F6BF EDE2 D016 D1B2 4F18 742E 2C8F B7EF

The SSL certificate sha1 fingerprint for the repositories:

e1:e6:41:96:3c:eb:ae:78:e2:73:0d:a2:32:2f:6b:21:13:bf:3d:0f

For people using svn+ssh, here's the fingerprint of the server's RSA key:

1e:89:fa:0d:c3:11:a4:81:36:84:b6:f2:6b:f0:5b:ad

The repository is organised in main directories:

#/branches
#/tags
#/trunk

You can explore the repository structure at [http://websvn.kde.org/ http://websvn.kde.org/]

 

=== The top-level directory /trunk ===

The <tt>/trunk</tt> top-level subdirectory is where the main development for KDE occurs. What you will find here is what will become the next KDE release and its associated programs. Here you will also find the <tt>www</tt> module, which contains webpages for KDE's site and related ones.

<tt>/trunk</tt> is further subdivided into these sub-directories:

*<tt>KDE/</tt> KDE itself, what will become the next public release. It contains the following modules:
**'''kdelibs''' - KDE basic libraries, used by all KDE programs
**'''kdebase''' - KDE base programs, like the KDE Control Center, Kicker (the panel) and Konqueror (the web browser)
**'''kdeaccessibility''' - Accessibility files
**'''kdeadmin''' - KDE Administration applications
**'''kdeartwork''' - Images, themes, sounds and other art files
**'''kdebindings''' - Bindings for languages other than C++
**'''kdeedu''' - KDE Educational applications
**'''kdegames''' - KDE Games
**'''kdegraphics''' - KDE Graphical applications
**'''kdemultimedia''' - KDE Multimedia applications
**'''kdenetwork''' - KDE Networking applications
**'''kdepim''' - KDE Personal Information Management applications
**'''kdepimlibs''' - Libraries used by KDE-PIM applications.
**'''kdesdk''' - KDE Software Development Kit applications
**'''kdetoys''' - KDE toy applications
**'''kdeutils''' - KDE General utilities
**'''kdewebdev''' - KDE Web development applications
*<tt>kde-common</tt>

:Common admin/ directory

*<tt>bugs/</tt>

:[http://bugs.kde.org/ Bugzilla] files

*<tt>developer.kde.org/</tt>

:The content of developer.kde.org

*<tt>extragear/</tt>

:KDE programs outside the main KDE releases.

*<tt>kdereview/</tt>

:Temporary home for KDE applications that are believed to have reached release-quality. From here, once all major issues are resolved, applications are moved either to <tt>/trunk/KDE/</tt> or to <tt>/trunk/extragear/</tt>

*<tt>kdesupport/</tt>

:Supporting applications and libraries for KDE

*<tt>koffice/</tt> The KDE Office suite, containing the programs:
**'''karbon'''
**'''kchart'''
**'''kexi'''
**'''kformula'''
**'''kivio'''
**'''koshell'''
**'''kplato'''
**'''kpresenter'''
**'''krita'''
**'''kspread'''
**'''kword'''
*<tt>konstruct/</tt>

:Konstruct, the KDE build program

*<tt>l10n-kde3/</tt>

:Translations for the "unstable" modules of KDE 3 (extragear, playground)

*<tt>l10n-kde4/</tt>

:Translations for KDE 4

*<tt>playground/</tt>

:The KDE playground: applications being developed, but not having yet reached release-quality.

*<tt>qt-copy/</tt>

:The convenience copy of [http://www.trolltech.com/ Trolltech's] Qt library, which KDE is based upon. Remember, this is deprecated, you should be using the git repository, kde-qt instead. Qt-copy is at version 4.5, yet trunk '''requires '''

*<tt>tests/</tt>

:khtml, KOffice and ksvg testcases

*<tt>valgrind/</tt>

:The Valgrind application, which is hosted on the KDE repository, but that is not part of KDE itself. Note that newer versions of Valgrind are developed on their own repository. The KDE Valgrind modules only holds up to Valgrind 2.4.

*<tt>www/</tt>

:Webpages for the KDE site (and related sites). Write access to this directory is restricted.

=== The top-level directory <tt>/tags</tt> ===

This directory contains the official releases of the programs maintained and developed in the KDE repository. Each individual application has a subdirectory here. Inside it, you will find the release numbers.

For instance, the KDE 3.4.0 code can be found under <tt>/tags/KDE/3.4.0/</tt>.

=== The top-level directory <tt>/branches</tt> ===

This directory contains the branch versions of the applications after a major release.

Most KDE applications adhere to the philosphy that new features (as well as new user-visible strings) are added only to the next release cycle — the one that lives in <tt>/trunk/</tt>. However, bugfixes are applied to all applications, even after release.

In order to do that, a branch is created at the moment of the release, indicating the state of the files at that time. Bugfixes are then checked in to those files. Those branches are the ones in <tt>/branches/</tt>.

For instance, the KDE 3.4.x branch can be found under <tt>/branches/KDE/3.4/</tt>

The subdirectories you will find inside <tt>/branches</tt> are the application subdirs, like <tt>akregator/</tt>, <tt>amarok/</tt>, <tt>arts/</tt>, <tt>k3b/</tt>, etc. You will also find a <tt>KDE/</tt> subdir, containing the official KDE releases since time immemorial.

One special subdir is found in <tt>/branches</tt>: <tt>work/</tt>. This subdir contains the so-called "work branches", that is, branches containing features being worked on, sometimes highly experimental. Multi-application work branches always are checked in to <tt>/branches/work/</tt>, but single-application branches may be found in each application's subdir. That is a decision left to the developers.

 

== Checking out and updating ==

=== Checking out ===

In order to check out something with Subversion, you use the <tt>checkout</tt> subcommand.

'''WARNING:''' If you checkout trunk/KDE/ or branches/KDE/foo/ you will download complete kde-i18n!

Suppose you wanted to check out only kdeedu from the KDE repository. You would do:

Subversion users currently using ssh access should use protocol svn+ssh while subversion users currently using password access should use protocol https in the following:

svn checkout --username=<username> <protocol>://svn.kde.org/home/kde/trunk/KDE/kdeedu

For checking out kdevelop from extragear you would do:

svn checkout --username=<username> <protocol>://svn.kde.org/home/kde/trunk/extragear/sdk/kdevelop

Note that you may wish to use the following if the above doesn't work:

svn checkout <protocol>://<username>@svn.kde.org/home/kde/trunk/extragear/sdk/kdevelop

=== Updating ===

In order to update, you use the <tt>update</tt> subcommand.

You change into your checked out copy (for those new to this whole process, the checked out copy should be in your Home folder) and issue a <tt>svn update</tt> (or, shorter, <tt>svn up</tt>) command.

== Knowing the status of a file ==

To know which local files you had modified, you have to do

svn status

and look at the files with '''M''' (for modified).

== Committing to the repository ==

Committing to the Subversion repository is accomplished with the <tt>commit</tt> (<tt>ci</tt> for short) subcommands:

svn commit
# or
svn ci
# or
svn ci filename.cpp

This way, <tt>svn</tt> will launch the editor specified in <tt>$SVN_EDITOR</tt> for you to compose the commit message. If you prefer, you can give <tt>svn</tt> the -m option with your full message:

svn ci -m "Updating protocol to conform to HTTP/1.1"

== Ignoring files ==

Subversion stores ignored files per directory. To edit the ignored files of the directory you are currently in, do

svn propedit svn:ignore .

that will launch your editor, write there the names of the files you want to ignore, one file per line. Once you are done, do a commit so the ignored list file gets updated on the server.

A lot of files were ignored in CVS with help from global ignore list which is not supported yet by SVN. You can wait for svn 1.3 or you need to add the ignore list to the [miscellany] group in your {{path|~/.subversion/config}} (all in one line):

global-ignores = *.o *.lo *.la .*.rej *.rej .*~ *~ .#* #*# .DS_Store *.moc
*.moc.cc *.moc.cpp config.log config.status config.cache *.gmo .deps .libs
SunWS_cache *.lo *.la *.rpo *.la.closure *_la_closure.cpp *_la_closure.cc
*_la_closure.cxx *.all_cc.cc *.all_cpp.cpp *.all_C.C *.all_cxx.cxx
*_meta_unload.cc *_meta_unload.h *_meta_unload.cpp *_meta_unload.C
*_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in Makefile.calls.in
Makefile.rules Makefile.calls autom4te.cache *.kidl

== Working with multiple revisions and branches ==

Unlike CVS, Subversion doesn't generate a revision number for each file modified. Instead, the full repository is versioned, as a whole. This way, a given revision number represents the state the repository was on a given date. In other words, a revision number is like a timestamp (in fact, the Subversion server uses this fact to search for dates in the repository faster).

So, for instance, when you check out the KDE repository, Subversion will tell you the following:

Updated to revision 403821.

This means that the latest revision available at the time of the operation was 403821. If you make a modification and commit, Subversion will update the server-side revision and will inform you of it. Like CVS, only the committed files will be updated: you will need run <tt>cvs up</tt> to update the rest of the files.

If you want to retrieve a specific revision of a file, you can use the <tt>-r</tt> switch. Besides the revision number itself, -r accepts a number of other possibilities:

*The revision number: for example, use -r 403819 to retrieve that version
*'''BASE''': the revision you updated to
*'''COMMITTED''': the revision a file was last modified, before BASE
*'''PREV''': the revision of the previous commit to the file before COMMITTED
*'''HEAD''': the most recent revision available in the server
*'''{ date }''': between curly brackets, you can specify a date for searching the closest revisions

The following illustrates the evolution of the keywords:

#You run <tt>svn up</tt> to update to the latest available revision. Suppose Subversion tells you it updated to revision 403821. This means that HEAD and BASE are 403821.
#You modify file README and commit it. Suppose Subversion tells you it committed revision 403822. This means HEAD, BASE and COMMITTED are 403822.
#You modify the file again and commit it. Now PREV is 403822, but HEAD, BASE and COMMITTED are updated to a new value (suppose it's 403823).
#Now someone else modifies the repository, and you update your working copy. If Subversion tells you it updated to 403824, this means now HEAD and BASE are moved to 403824 (but PREV and COMMITTED stay the same)
#If someone modifies the README file now, HEAD is moved. The other keywords stay the same for you, until you update. At this time, we will have HEAD = 403825 (the latest available revision), BASE = 403824 (the revision you last updated to), COMMITTED = 403823 (the revision of the latest change to the file when you last updated) and PREV = 403822 (the revision of the change before COMMITTED)

Those keywords are useful to retrieve logs and diffs for commits to the repository.

If you want to see the difference between your working copy and BASE, you can run:

svn diff

This is a very fast operation, since Subversion keeps a local copy of BASE. It doesn't need a network connection to accomplish this operation.

If you want to see the difference between your local copy and the latest available on the server, you will run:

svn diff -r HEAD

If you want to see what has changed in the repository since you've last updated, you can use:

svn diff -r BASE:HEAD

If you want to see the last change to a file before BASE, you can use:

svn diff -r PREV:BASE
# or
svn diff -r PREV:COMMITTED

That is also valid for the <tt>svn log</tt> command.

== Linking in subdirectories from other places ==

It can happen you would like to include a copy of a subdirectory from another place, but just for convenience, not for developing the code in there. Of course it should be updated automatically whenever the original changes. Subversion can help you. You need to edit the property <tt>svn:external</tt> of the directory the subdirectory should be added to. So for the current directory you use

svn propedit svn:externals .

and then enter lines of the form

libkhalkhi svn://anonsvn.kde.org/home/kde/trunk/playground/pim/khalkhi

Updating will now fetch <tt>/trunk/playground/pim/khalkhi</tt> into the subdirectoy <tt>libkhalkhi</tt>.

{{warning|Beware that you cannot commit changes you did to the local copy of the external subdirectory, it is just a readonly copy.}}

You use <tt>svn://anonsvn.kde.org</tt> and not another protocol, because <tt>anonsvn.kde.org</tt> is accessible to everyone. Using <tt>https:</tt> or <tt>svn+ssh:</tt> would only work for users of that protocol. There are still some small disadvantage with <tt>anonsvn.kde.org</tt>: It is not always in synchronization with <tt>svn.kde.org</tt>, so updates in the original branch may take a while to appear on <tt>anonsvn.kde.org</tt>. And some strict firewalls are blocking the <tt>svn:</tt> protocol.

A special case in KDE 3 is the subdirectory <tt>admin</tt>, containing the KDE 3 build utilities. It is linked in to the top directory in all modules, and maintained in <tt>/branches/KDE/3.5/kde-common</tt>. For <tt>admin</tt> the KDE subversion server is configured to allow readonly access for everyone, so if you see

admin https://svn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin

there is no need to change this.

== Further Links ==

*[[Development/Tools/svnmerge.py|Merge tracking with svnmerge.py]]

= Old Getting_started/Sources/Anonymous SVN Page =

== Abstract ==

For those of us that like to stay on the "bleeding edge" there's an easy way to keep a local copy of the KDE sources up-to-date — anonymous SVN.

Alternatively, install [[Getting_Started/Distribution_Packages|KDE SVN packages from your distribution]].

== Anonymous SVN ==

=== Setup Subversion ===

First, install the subversion (svn) binary if it isn't already on your computer. Your operating system should have a package for it. Alternatively you can download and compile it yourself via the [http://subversion.tigris.org/project_packages.html svn project download page]. Please read the [[Getting_Started/Sources/Using_Subversion_with_KDE|KDE Subversion tutorial]] if you are interested in how to use Subversion.

=== Checkout KDE TRUNK ===

'''/trunk/''' is where the Qt4-based KDE 4 is being developed. The following is the minimal set of modules you will need to check out to build KDE and KDE software:

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase

You also need to checkout KDESupport:

svn co svn://anonsvn.kde.org/home/kde/trunk/kdesupport

{{tip|If your firewall doesn't allow access to arbitrary ports, substitute '''svn://anonsvn.kde.org/''' with '''svn://anonsvn4.kde.org:443/''' above.}}

{{tip|The kdebase module has an external dependency, using svn:externals. The problem is, at this time, the externals property is set with an absolute path, pointing to anonsvn. For those using behind a firewall, this is a problem. You can change the property for your workspace, using two commands:
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|cs]] KDE
svn propset svn:externals "lib svn://websvn.kde.org:443/home/kde/trunk/KDE/kdebase/runtime/kstyles/oxygen/lib" kdebase/workspace/kwin/clients/oxygen
svn propset svn:externals "lib svn://websvn.kde.org:443/home/kde/trunk/KDE/kdebase/runtime/kstyles/oxygen/lib" kdebase/workspace/kwin/clients/ozone
This way the external property will look for the additional files in the websvn repository. There are also kdenetwork/kget/transfer-plugins/bittorrent and kdebase/workspace/kwin/clients/ozone that use svn:externals get the url with svn propget svn:externals PATH and replace anonsvn.kde.org with websvn.kde.org:443 here too.}}

'''qt-copy''' is a copy of the latest stable [http://www.trolltech.com Qt] release which works with KDE, put into SVN for convenience. It also contains patches by KDE developers that haven't found their way to Qt yet. They are recommended for those working with KDE from '''trunk'''. Instructions on how to get and configure it can be found [[Getting_Started/Build/Qt |here]].

{{tip| It is recommended to use kde-qt.git instead of qt-copy.

git clone git://gitorious.org/+kde-developers/qt/kde-qt.git qt-kde

}}

If you wish to have a complete copy of KDE TRUNK, you can simply check out the entire source tree with one command:

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE

{{note|It is smarter to first use [http://websvn.kde.org/trunk/KDE The KDE Source Repository Web Viewer]. Use it to choose which modules to download. This way KDE will be quicker to install and try out.}}

If you want additional software packages you can check out the following modules within '''trunk/''' as well:

koffice
extragear
playground
kdereview

So, for example, if you want to check out koffice trunk, you can use:

svn co svn://anonsvn.kde.org/home/kde/trunk/koffice

=== Checking out trunk using snapshots ===

If you are checking out modules from '''trunk/''' you may be able to save time by using snapshots. Using Subversion trunk snapshots is described at [[../Snapshots|the Subversion snapshots tutorial page]].

=== Checking out KDE 3 instead ===

If you want to track KDE 3 rather than the bleeding edge, you may retrieve the KDE 3.5 sources using:

svn co svn://anonsvn.kde.org/home/kde/branches/arts/1.5/arts
svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/

And if you want the matching qt-copy:
svn co svn://anonsvn.kde.org/home/kde/branches/qt/3.3/qt-copy

=== Checking out specific releases ===

KDE modules are also tagged at each release so that it is possible to get a specific release of KDE. Most KDE modules have a tag name in the format '''tags/KDE/X.Y.Z''' (where X, Y and Z represent the exact version). The arts module (only needed for KDE 2 and KDE 3) has a different format of tag name, '''tags/arts/X.Y.Z'''. For instance to get kdelibs as it was shipped in KDE 3.5.0, do:

svn co svn://anonsvn.kde.org/home/kde/tags/KDE/3.5.0/kdelibs/

If you then want to update this checkout to KDE 3.5.5, use this command:

svn switch svn://anonsvn.kde.org/home/kde/tags/KDE/3.5.5/kdelibs

{{tip|If you used a '''/branch/''' or '''/trunk/''' path, then there is no need to switch, just run '''svn update'''.}}

=== Checking out translations ===
If you are looking for translations and other localizations, check out the appropriate language from the appropriate module: [http://websvn.kde.org/trunk/l10n-kde4 l10n-kde4] (KDE4) or [http://websvn.kde.org/trunk/l10n-kde3 l10n-kde3] (KDE3).

{{Warning|The l10n module is ''extremely'' large. Be sure you have lots of time and disk space on hand before checking out the entire l10n module. Most people only check out specific language subdirectories rather than the entire l10n module.}}

You are now ready to start building KDE! Visit [[Getting_Started/Build|this page]] for instructions on building trunk or [[Getting_Started/Build/Stable_Version|this page]] for instruction on compiling the last stable release.

=== Checkout from behind a proxy ===

If the tip above didn't help you, and you've realized that the only way to go seems to be with http://anonsvn.kde.org/.. , then you will have to jump through a few hoops to get an svn checkout. Since http:// access is open only to developers, you will have to use svn://. Transconnect is a small piece of software that can tunnel all the traffic through your friendly neigbourhood proxy server. Get the transconnect sources from http://transconnect.sourceforge.net/ , compile it, and edit ~/.tconn/tconn.conf to point to your proxy server. Export the LD_PRELOAD variable as per the README from transconnect, and you're set to go.

== Also of interest ==
* Visit http://websvn.kde.org/ to browse the source code online.
* anonsvn.kde.org is a round robin DNS entry, which will resolve to one out of several anonsvn mirrors. The DNS setup is maintained by [mailto:sysadmin@kde.org the KDE sysadmins]. However, it might be desireable to choose a local mirror explicitely. Some mirrors are listed below, sorted by performance:
** kde.mneisen.org is located near Nuernberg, Germany, maintained by [mailto:martin.eisenhardt@mneisen.org Martin Eisenhardt]
** www.englishbreakfastnetwork.org also hosts an anonymous SVN mirror, at the University of Nijmegen, Netherlands. Maintained by [mailto:groot@kde.org Adriaan de Groot]

* There are also aliases anonsvn1.kde.org, anonsvn2.kde.org and anonsvn3.kde.org which point to the mirrors used in the DNS round robin (the above two plus another mneisen.org mirror). If you experience trouble because one mirror is broken, you can always select a specific mirror using either the fullnames above or simply anonsvn1, 2, or 3.

: Be careful when switching between mirrors. SVN remembers the server in the working copy, so to switch you have to run
svn switch --relocate svn://anonsvn.kde.org/ svn://kde.mneisen.org/
: in all your checkouts.
If you're interested in setting up a svn mirror, please contact [mailto:sysadmin@kde.org the KDE sysadmins].

[[Category:Build KDE]]

Projects/MoveToGit/UsingSvn2Git

2012-09-14T17:38:54Z

Nicolás: /* Servers to use for all developers */ we have only one server now

This page documents how to go about getting a KDE module ready for the Great Git Migration of 2010.

=== Servers to use for all developers ===

KDE Sysadmin provides a server which is fully setup for writing rules. You can find more information about that on: http://community.kde.org/Sysadmin/DeveloperAccessForRuleWriting.

All registered KDE developers have access to this machine. The rest of this document assumes a setup on your local computer. You are free to set it up on your local computer, but there is no need to. You can use the server provided by KDE Sysadmin.

=== Getting the tools ===

The necessary tools are hosted at [http://www.gitorious.org/svn2git http://www.gitorious.org/svn2git] and [https://projects.kde.org/projects/playground/sdk/kde-ruleset https://projects.kde.org/projects/playground/sdk/kde-ruleset]. To get started do:

<syntaxhighlight lang="bash">
git clone git://gitorious.org/svn2git/svn2git.git
git clone git://anongit.kde.org/kde-ruleset
</syntaxhighlight>

And then install the libsvn-dev package.

This will get you the source code to build svn2git and the KDE ruleset files as they currently exist. Build the svn2git tool before moving on to the next step.

==== Building svn2git ====
Make sure you have Qt4 installed, then simply issue
<nowiki>qmake && make</nowiki> to build the executable called "svn-all-fast-export"

=== How rulesets work ===
The format for the svn2git rules is pretty simple. First and foremost you
have to declare some repositories:

<pre>
create repository kdelibs
end repository
</pre>

This tells svn2git that it should create a git repository called "kdelibs" that we can later on use to put commits into it.

The rest of the file are rules matching specific paths in Subversion, each rule
specifies what to do with the commits that appeared at the given path. The
possible actions are ignoring them or adding them to a particular branch in a particular repository. '''Note:''' Ignoring is done by simply leaving out the information about the repository and the branch.

As examples are more explanatory, the following rule would put all commits from 123453 to 456789 from the path /trunk/KDE/kdelibs into the master branch of
the kdelibs repository:
<pre>
match /trunk/KDE/kdelibs/
min revision 123453
max revision 456789
repository kdelibs
branch master
end match
</pre>

The min and max revision are useful in cases where the same path in SVN contains
code for different branches. An example would be KDevelop3, where KDevelop 3.3 was shipped with KDE 3.5 until 3.5.7, 3.5.8 contained KDevelop 3.4 and 3.5.9 contained KDevelop 3.5 and all of those kdevelop versions are now under /branches/KDE/3.5/kdevelop.

The two revision parameters are however not mandatory, if they're left out, then all commits that went to the given matching path in SVN are taken over into the specified branch.

To generate tags with git you use a special format for the branch parameter: refs/tags/<tagname>. So to put all commits from /tags/KDE/4.4.0/kdelibs into the v4.4.0 tag in the kdelibs git repository the rule would be like this:

<pre>
match /tags/KDE/4.4.0/kdelibs/
repository kdelibs
branch refs/tags/v4.4.0
end match
</pre>

For more examples see the svn2git/samples/ directory and the rules in the kde-ruleset repository.

The recurse action is a hack to tell svn2git to recurse into a directory it has just copied or that existed because it is of interest. Example: if we are importing kdelibs, it exists in {{path|trunk/KDE/kdelibs}}. At branching, someone did: <syntaxhighlight lang="bash">svn cp $SVNROOT/trunk/KDE $SVNROOT/branches/KDE/4.4</syntaxhighlight>

SVN recorded in that commit that branches/KDE/4.4 was the only path changed.
That means the rule <pre>branches/KDE/[^/]+/kdelibs/</pre> will not match.

We need to tell the tool that something interesting happened inside and it
should recurse. Then it will apply again all rules to the files that exist at
that point, at which point the rules will match.

==== Important Details ====

* All rules matching directories need to end with a '/', else the tool will crash at some point. This is a known bug. The only exception are the rules using the recurse-action.

* All rules matching files need to use the prefix rule.

* Matching rules can use Regular Expressions (according to the QRegExp syntax) in the match line and can use backreferences in the repository, prefix and branch parameters using \n (n=1,2,3,...) to reduce the amount of rules.

* The rules form an ordered list that the tool goes through while matching the changed paths for each commit. So if two rules match the same path and neither of the two has more matching criteria, then the rule that is written further up in the file wins. This is useful to exclude certain commits from the extraction process, if you look at the existing kde ruleset you'll notice that at the top some revisions are ignored.

* Each rule file needs to handle all commits, ie. each file should end with a rule which matches everything and does nothing.

=== Setting up your system ===

You will need ~65GB of disk space to get started, as the process requires a copy of the KDE svn database. There is a script that will download this for you (and which can be used to update it periodically using rsync) in kde-ruleset/bin/startSync.

more stuff goes here ...

=== Step-by-Step on writing rules for a module ===

==== Analyzing Subversion history to write rules ====
First of all you should check whether there are already rules for this module in the kde-ruleset repository. If there are rules already please go down to "Running svn2git"

If there are no rules yet, lets start with the master (aka trunk) branch. The easiest way to find out history with svn is executing:
<pre>svn log -v --stop-on-copy file:///path/to/svn/trunk/KDE/module</pre>

Please note that '/path/to/svn/' is the path to the 65GB you downloaded, and the 'trunk/KDE/module' is the module you want to write rules for, but those two put together is *not* a path that physically exists on your disk. svn log is smart enough to do what you want.

This will give you a history of the given module in trunk, it'll stop on the first commit that copied the code from somewhere else. The verbose output will allow you to see where this copy came from.

Now we have a starting point to write a rule, we want all commits from this path in our module repository in the master branch:
<pre>
match /trunk/KDE/module/
repository module
branch master
end match
</pre>
If the log stops at a commit that copied the module from somewhere, we need to
follow this to also get the history imported from the "old" place the module resided. The same svn command can be used with slightly different path argument:

<pre>svn log -v --stop-on-copy file:///path/to/svn/some/other/path@revision</pre>
The @revision is important as the original path usually doesn't exist anymore. With this we can write the next rule to the rules file and repeat until we've finally reached the point where the code was initially imported into svn (or probably cvs in the old days)

Now we can take care of the branches, this is a bit more involved as there may be multiple branches scattered over the /branches directory in svn. You can use the same commands as before to find out the history of a branch if you know the path. This time however you can stop following the source of copy-operations once you've found a source that you've already matched in a rule. That way your branch will be connected to the branch it originated from (which is often trunk aka master) in git.

A useful help with finding branches is svn ls in combination with the path@revision syntax, that way you can view the content of a particular svn directory as it was in an older revision. With this you can even find branches that are not visible (have been deleted) in the current revision.

The rule for putting commits into a git branch in the final repository is only slightly different (the example is for a core module):
<pre>
match /branches/KDE/4.4/module
repository module
branch 4.4
end match
</pre>

And last are the tags, this works the same as branches and trunk, except for using branch refs/tags/v<tag-version> for the branch parameter.

==== Running svn2git ====
This is the easiest, but most time-consuming part. As example lets say that in our current working directory we have the kde rules repository in kde-ruleset subdir, the svn2git tool in the svn2git subdir and the KDE repository in the svn subdir:
<pre>
svn2git/svn-all-fast-export --identity-map kde-ruleset/account-map --rules kde-ruleset/module svn
</pre>

This will take a few hours usually, but it'll spit out the progress. The tool also writes a logfile to module.log, so in case something goes wrong you can find more details in there.

Once its done you should have a new "module" git repository in your current working directory.

==== Post-processing ====
Some problems that might occur in the converted git repository can be fixed after the actual conversion. More specifically, these are wrong parents and empty commit objects for tags.

Wrong parents can be handled using a parent map. This is a file with each line in the format "parent-id child-id", where both ids are the integer numbers of the corresponding svn commit. You can also add newlines and comments starting with #. Each line in the parent map adds an edge in the commit graph from parent to child. This is frequently necessary to correctly reflect merges in the git history. Occasionally, svn2git might add a parent which should not be a parent at all. In this case, you can write a line "clear child-id" to delete that edge, and afterwards add the correct edge as explained above. It is usually easiest to first do a conversion, then look at the result with "gitk --all" and if something is wrong find the svn ids from the git commit message.

To actually perform the fix, run "kde-ruleset/bin/parent-adder $parent_map_file" in the new git repository. You should probably make a backup of the git repository before, as rerunning the conversion would take a lot of time if something goes wrong.

Empty commit objects for tags can be fixed by running "kde-ruleset/bin/fix-tags" in the git repository.

Both processes leave a backup of the original commit objects. These can be removed with "kde-ruleset/bin/remove-fb-backup-refs.sh".

==== Checking for proper history in the new git repository ====
To check the history of the created git repository simply change into the directory and use your favourite git command like ''git log'' to check if all is well.

A '''very easy way to check whether the history was imported properly''' is to use the gitk tool from git. It shows you a graphical representation of the history in the git repository which makes it easy to identify where something is wrong.

The tool should be run with the --all switch so it shows all branches.

You can now scroll through the history to check whether things have been imported correctly.

First and foremost there should be the master branch starting at the top with the most recent commit to trunk/ and ending in the oldest commit that imported the code into KDE's svn or cvs repository.

From the master branch there should be several branches going away for each branch you imported. And eventually also branches that start from another non-master branch.

Things that you should look out for are branches that start "nowhere", that is the first commit in the branch has no parent in another branch or master. This means that svn2git didn't see a commit that created this branch from another using a svn cp command. That can mean that you may have forgotton to add a match rule for some path or that the same path was used for different branches in different revisions. The same applies to tags which have a commit without any parent.

This can usually be fixed by using svn log and svn ls to follow the history of the branch. Eventually you might need to apply the min/max revision paramters.

You'll notice that some tags are looking like this:

<pre>
|
* * <v1.2.3>
| |
* *
| /
*
</pre>

Thats normal for our tags even if a bit ugly. The reason is that often compile-fixes are done in trunk/ after the tag has been created and then the commit has been merged over to the tag.

Another thing however are tags that are named vx.y.z_124321. These are tags that have been deleted and re-created later. You can usually see that in the svn log history, these tags can either be manually deleted after the repository creation using git tag or you can add rules that ignore certain revisions of the tag-path before the one putting the commits into the git repository:

<pre>
match /tags/KDE/3.3.2/kdelibs
min revision 424234
max revision 424236
end match
match /tags/KDE/3.3.2/kdelibs
repository kdelibs
branch refs/tags/3.3.2
end match
</pre>

If you choose to delete them manually please make sure to document this with a textfile or inside the rule file so if someone else does the conversion later again he'll know what manual steps you did.

Also try grepping the output from svn2git for the string '"copy from"' (with the double quotation marks). This will give you a list of revisions/paths that svn2git could not detect the origin of. That is someone did a svn cp/mv and the old path is not in the generated git repository.

Before publishing the newly created git repository make sure to repack it. This can greatly reduce it's size (i.e. Phonon's git repository could be shrunken from 18 MB to 5.2 MB)

==== Pushing the Repository to git.kde.org ====
Request a new project as described in the [http://community.kde.org/Sysadmin/GitFAQ#Requesting_project_migrations_from_KDE_SVN_or_Gitorious.org Git KDE Manual]. Then push the repository into that new git project.

==== How to update the account-map file ====

Currently, account-map file is being generated with 'generateAccountMap'[http://gitorious.org/svn2git/kde-ruleset/blobs/master/bin/generateAccountMap] script which parses kde-common/accounts[http://websvn.kde.org/trunk/kde-common/accounts?view=log] and kde-common/disabled-accounts[http://websvn.kde.org/trunk/kde-common/disabled-accounts?view=log] from SVN.

Once you have your git repository you should check if there are accounts not listed in account-map file (you can use checkMissingAccounts[http://gitorious.org/svn2git/kde-ruleset/blobs/master/bin/checkMissingAccounts]), if that is the case, check if the missing accounts are listed in kde-common/accounts or kde-common/disabled-accounts, if it's not there file a sysadmin bug report[https://bugs.kde.org/enter_sysadmin_request.cgi] to get your missing account included in disabled-accounts. Once you get your missing accounts included in disabled accounts, you could generate the account-map file running 'bin/generateAccountMap', then run svn-all-fast-export again. Do not edit account-map file directly!

=== Troubleshooting ===

==== Recurse action doesn't work with cvs2svn tag commits ====

You may have to deal with a commit done by cvs2svn to create a tag, for example:
<pre>
r386536 | (no author) | 2005-02-05 22:16:00 +0100 (Sat, 05 Feb 2005) | 2 lines
Changed paths:
A /branches/beta_0_7_branch (from /trunk:386535)
D /branches/beta_0_7_branch/art-devel
D /branches/beta_0_7_branch/arts
D /branches/beta_0_7_branch/bugs
D /branches/beta_0_7_branch/devel-home
D /branches/beta_0_7_branch/developer.kde.org
D /branches/beta_0_7_branch/enterprise.kde.org
D /branches/beta_0_7_branch/events.kde.org
D /branches/beta_0_7_branch/foundation
D /branches/beta_0_7_branch/kckde
D /branches/beta_0_7_branch/kde-common
D /branches/beta_0_7_branch/kde-i18n
D /branches/beta_0_7_branch/kde-qt-addon
D /branches/beta_0_7_branch/kde-women.kde.org
D /branches/beta_0_7_branch/kdeaccessibility
D /branches/beta_0_7_branch/kdeaddons
D /branches/beta_0_7_branch/kdeadmin
D /branches/beta_0_7_branch/kdeartwork
D /branches/beta_0_7_branch/kdebase
D /branches/beta_0_7_branch/kdebindings
D /branches/beta_0_7_branch/kdeedu
D /branches/beta_0_7_branch/kdeextragear-1
D /branches/beta_0_7_branch/kdeextragear-2
M /branches/beta_0_7_branch/kdeextragear-3
D /branches/beta_0_7_branch/kdeextragear-3/Makefile.am.in
D /branches/beta_0_7_branch/kdeextragear-3/Makefile.cvs
D /branches/beta_0_7_branch/kdeextragear-3/README
D /branches/beta_0_7_branch/kdeextragear-3/configure.in.bot
D /branches/beta_0_7_branch/kdeextragear-3/configure.in.in
D /branches/beta_0_7_branch/kdeextragear-3/digikam
D /branches/beta_0_7_branch/kdeextragear-3/digikamimageplugins
D /branches/beta_0_7_branch/kdeextragear-3/doc
D /branches/beta_0_7_branch/kdeextragear-3/filelight
D /branches/beta_0_7_branch/kdeextragear-3/kcfgcreator
D /branches/beta_0_7_branch/kdeextragear-3/kconfigeditor
D /branches/beta_0_7_branch/kdeextragear-3/kdebluetooth
D /branches/beta_0_7_branch/kdeextragear-3/kdetv
D /branches/beta_0_7_branch/kdeextragear-3/keurocalc
D /branches/beta_0_7_branch/kdeextragear-3/kiosktool
D /branches/beta_0_7_branch/kdeextragear-3/klicker
D /branches/beta_0_7_branch/kdeextragear-3/kplayer
D /branches/beta_0_7_branch/kdeextragear-3/pwmanager
D /branches/beta_0_7_branch/kdeextragear-libs-1
D /branches/beta_0_7_branch/kdegames
D /branches/beta_0_7_branch/kdegraphics
D /branches/beta_0_7_branch/kdeinstaller
D /branches/beta_0_7_branch/kdejava
D /branches/beta_0_7_branch/kdekiosk
D /branches/beta_0_7_branch/kdelibs
D /branches/beta_0_7_branch/kdemultimedia
D /branches/beta_0_7_branch/kdenetwork
D /branches/beta_0_7_branch/kdenonbeta
D /branches/beta_0_7_branch/kdenox
D /branches/beta_0_7_branch/kdepim
D /branches/beta_0_7_branch/kdeplayground-artwork
D /branches/beta_0_7_branch/kdeplayground-base
D /branches/beta_0_7_branch/kdeplayground-edu
D /branches/beta_0_7_branch/kdeplayground-games
D /branches/beta_0_7_branch/kdeplayground-ioslaves
D /branches/beta_0_7_branch/kdeplayground-multimedia
D /branches/beta_0_7_branch/kdeplayground-network
D /branches/beta_0_7_branch/kdeplayground-pim
D /branches/beta_0_7_branch/kdeplayground-utils
D /branches/beta_0_7_branch/kdereview
D /branches/beta_0_7_branch/kdesdk
D /branches/beta_0_7_branch/kdesecurity
D /branches/beta_0_7_branch/kdesupport
D /branches/beta_0_7_branch/kdetoys
D /branches/beta_0_7_branch/kdeutils
D /branches/beta_0_7_branch/kdevelop
D /branches/beta_0_7_branch/kdewebdev
D /branches/beta_0_7_branch/kdoc
D /branches/beta_0_7_branch/kfte
D /branches/beta_0_7_branch/khtmltests
D /branches/beta_0_7_branch/klyx
D /branches/beta_0_7_branch/kmusic
D /branches/beta_0_7_branch/koffice
D /branches/beta_0_7_branch/kofficetests
D /branches/beta_0_7_branch/konstruct
D /branches/beta_0_7_branch/qt-copy
D /branches/beta_0_7_branch/quanta
D /branches/beta_0_7_branch/sysconfig
D /branches/beta_0_7_branch/valgrind
D /branches/beta_0_7_branch/www

This commit was manufactured by cvs2svn to create branch
'beta_0_7_branch'.
</pre>
If you do this
<pre>
match /branches/beta_0_7_branch/kdeextragear-3/krecipes/
repository krecipes
branch 0.7
end match

match /branches/beta_0_7_branch/
min revision 386536
max revision 386536
action recurse
end match
</pre>
svn-all-fast-export will fail, you'll get an error sayining that '/foo/bar/path' was not found where '/foo/bar/path' is one of the deleted paths in the cvs2svn commit. This is because some paths were deleted in the same commit where you want to do an 'action recurse'. Therefore, to avoid matching the deleted paths you should do an action recurse on each intermediate directory from '/branches/beta_0_7_branch/' to '/branches/beta_0_7_branch/kdeextragear-3/krecipes/' and you should use a final '$' to make sure that the deleted paths will not be considered, thusly:
<pre>
match /branches/beta_0_7_branch/kdeextragear-3/krecipes/
repository krecipes
branch 0.7
end match

match /branches/beta_0_7_branch/kdeextragear-3/$
min revision 386536
max revision 386536
action recurse
end match

match /branches/beta_0_7_branch/$
min revision 386536
max revision 386536
action recurse
end match
</pre>

=== Getting Help ===
If you run into strange things or can't find a rule for something you can reach the KDE Git migration team on IRC: irc.freenode.org, #kde-git or on the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest mailinglist]

Schedules/Extragear

2012-08-14T21:01:36Z

Nicolás: Add calligra info

This page is intended to be a central location for Extragear projects to keep users and contributors (translators, packagers, etc.) informed about upcoming releases in a very accessible way.

 

{| border="1"
|-
! Project
! Next release (roughly)
! Next Release Code branch
! Next Release Translation branch
! Comments
|-
| K3b
| 1 March 2010
| [http://websvn.kde.org/trunk/extragear/multimedia/k3b/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-multimedia/ trunk kde4]
| String freeze starting from January 31 2010 (in effect)
|-
| KAudiocreator
|
|
|
|
|-
| Kaffeine
|
|
|
|
|-
| [http://extragear.kde.org/apps/kcoloredit/ KColorEdit]
| KDE release
| [http://websvn.kde.org/trunk/extragear/graphics/kcoloredit/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-graphics/ trunk kde4]
|
|-
| [http://www.kde-apps.org/content/show.php/KDE+Partition+Manager?content=89595 KDE Partition Manager]
| Q2/2010
| [http://websvn.kde.org/trunk/extragear/sysadmin/partitionmanager/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-sysadmin/ trunk kde4]
| 
|
|-
| [http://ww.kdevelop.org KDevelop]
| 1 May 2010
| [http://websvn.kde.org/trunk/extragear/sdk/kdevelop/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-sdk/ trunk kde4]
| string freeze starting 31 March 2010
|-
| KDiff3
| January 31, 2009
| [http://websvn.kde.org/trunk/extragear/utils/kdiff3/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-utils/ trunk kde4]
|
|-
| KFax
| KDE release
|
|
|
|-
| KFTPGrabber
|
|
|
|
|-
| KGrab
| KDE release
|
|
|
|-
| [http://extragear.kde.org/apps/kgraphviewer/ KGraphViewer]
| KDE release
| [http://websvn.kde.org/trunk/extragear/graphics/kgraphviewer/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-graphics/ trunk kde4]
|
|-
| KIconedit
| KDE release
|
|
|
|-
| [http://www.kmldonkey.org KMLDonkey]
| KDE release
| [http://websvn.kde.org/trunk/extragear/network/kmldonkey/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-network/ trunk kde4]
|
|-
| KNemo
| January 17, 2010
| [http://websvn.kde.org/trunk/extragear/network/knemo/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-network/ trunk kde4]
| String freeze in effect
|
|-
| KPager
|
|
|
|
|-
| KPhotoalbum
| May 9 2009
| trunk
| trunk
| Message freeze, April 3 2009
|-
| KPlayer
|
|
|
|
|-
| KPovmodeler
| KDE release
|
|
|
|-
| KRecipes
| 2.0, date unknown
| [https://projects.kde.org/projects/extragear/utils/krecipes/repository/?rev=2.0 git 2.0]
| [http://websvn.kde.org/branches/stable/l10n-kde4/templates/messages/extragear-utils/ stable]
| GUI strings frozen, docs ''not'' frozen
|-
| KSig
|
|
|
|
|-
| [http://ktorrent.org/ KTorrent]
| 8 november 2009
| [http://websvn.kde.org/branches/stable/extragear-kde4/network/ktorrent stable kde4]
| [http://websvn.kde.org/branches/stable/l10n-kde4/templates/messages/extragear-network/ stable kde4]
| String freeze in effect
|-
| Kuickshow
|
|
|
|
|-
| Muon Suite
| Final Release: August 2012, pre-releases monthly
|
|
|
|-
| KWlan
|
|
|
|
|-
| RSIBreak
|
|
|
|
|-
| Skanlite
| KDE release
| trunk
|
|
|-
| [http://skrooge.org Skrooge]
| 2010-02-06 (version 0.6.0)
| [http://websvn.kde.org/trunk/extragear/office/skrooge trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-office/ trunk kde4]
| String freeze in effect
|-
| [http://www.kde-apps.org/content/show.php?content=29153 Yakuake]
| July 8th, 2010
| [http://websvn.kde.org/trunk/extragear/utils/yakuake/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-utils/ trunk kde4]
| String freeze started June 24th, 2010
|-
| Kile
| June 8th, 2011 (Version 2.1)
|
|
| String freeze started 23 May 2011
|-
| [http://www.krusader.org/ Krusader]
| 2.4.0-beta1 released on June 26, 2011.
| [http://websvn.kde.org/trunk/extragear/utils/krusader/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-utils/ trunk kde4]
| String freeze since June 26, 2011 until 2.4.0 release.
|-
| BlueDevil
| 1.0.5 (stable) and 1.1.1 (trunk) released planned on July 15, 2011.
|
| stable, trunk
| String freeze since June 29, 2011 until 1.0.5 and 1.1.1 releases.
|-
| [http://amarok.kde.org/ Amarok]
| Early 2013
| git master
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-multimedia/ trunk kde4]
|
|-
| [http://digikam.org digiKam]
| July 27th 2011 [http://www.digikam.org/drupal/about/releaseplan]
| [https://projects.kde.org/projects/extragear/graphics git master]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-graphics/ trunk kde4]
| String freeze starting June 30th 2011.
|-
| [http://techbase.kde.org/Projects/KMyMoney KMyMoney]
| 4.6.1 from Stable around November 5th, 2011
| [http://websvn.kde.org/trunk/extragear/office/kmymoney/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-office/ trunk kde4]
| String freeze started October 22nd, 2011
|-
| massif-visualizer
| 0.3 is planned to be released on September 4, 2011
|
|
| String freeze started on August 8, 2011
|-
| [http://tellico-project.org Tellico]
| 2.3.4
| [http://websvn.kde.org/trunk/extragear/office/tellico/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-office/ trunk kde4]
| String freeze: September 5th, 2011 -- September 18th, 2011.
|-
| [http://www.rekonq.sourceforge.net rekonq]
| ~ October 11, 2011 (Version 0.8)
| [http://gitorious.org/rekonq/mainline/trees/master git master]
| [http://gitorious.org/rekonq/mainline/trees/master git master]
| String freeze for 3 weeks starting September 21, 2011 (0.8 release)
|-
| KDE Telepathy
| November 18th, 2011 (version 0.2)
|
|
| String freeze starting October 26th, 2011.
|-
| Calligra
| Calligra 2.6 planned for December 2012
|
|
| String freeze starting October 12th, 2011.
|-
| [http://konversation.kde.org Konversation]
| In the first week of December, 2011
| [http://gitorious.org/konversation/konversation/trees/master git master]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-network/ trunk kde4]
| String freeze started on November 17th, 2011.
|-
| Wicd Client KDE
| 17th of December, 2011 (version 0.3)
|
|
| String freeze started on December 6th, 2011.
|}

Schedules/Extragear

2012-08-14T20:06:19Z

Nicolás: Change link for krecipes i18n

This page is intended to be a central location for Extragear projects to keep users and contributors (translators, packagers, etc.) informed about upcoming releases in a very accessible way.

 

{| border="1"
|-
! Project
! Next release (roughly)
! Next Release Code branch
! Next Release Translation branch
! Comments
|-
| K3b
| 1 March 2010
| [http://websvn.kde.org/trunk/extragear/multimedia/k3b/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-multimedia/ trunk kde4]
| String freeze starting from January 31 2010 (in effect)
|-
| KAudiocreator
|
|
|
|
|-
| Kaffeine
|
|
|
|
|-
| [http://extragear.kde.org/apps/kcoloredit/ KColorEdit]
| KDE release
| [http://websvn.kde.org/trunk/extragear/graphics/kcoloredit/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-graphics/ trunk kde4]
|
|-
| [http://www.kde-apps.org/content/show.php/KDE+Partition+Manager?content=89595 KDE Partition Manager]
| Q2/2010
| [http://websvn.kde.org/trunk/extragear/sysadmin/partitionmanager/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-sysadmin/ trunk kde4]
| 
|
|-
| [http://ww.kdevelop.org KDevelop]
| 1 May 2010
| [http://websvn.kde.org/trunk/extragear/sdk/kdevelop/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-sdk/ trunk kde4]
| string freeze starting 31 March 2010
|-
| KDiff3
| January 31, 2009
| [http://websvn.kde.org/trunk/extragear/utils/kdiff3/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-utils/ trunk kde4]
|
|-
| KFax
| KDE release
|
|
|
|-
| KFTPGrabber
|
|
|
|
|-
| KGrab
| KDE release
|
|
|
|-
| [http://extragear.kde.org/apps/kgraphviewer/ KGraphViewer]
| KDE release
| [http://websvn.kde.org/trunk/extragear/graphics/kgraphviewer/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-graphics/ trunk kde4]
|
|-
| KIconedit
| KDE release
|
|
|
|-
| [http://www.kmldonkey.org KMLDonkey]
| KDE release
| [http://websvn.kde.org/trunk/extragear/network/kmldonkey/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-network/ trunk kde4]
|
|-
| KNemo
| January 17, 2010
| [http://websvn.kde.org/trunk/extragear/network/knemo/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-network/ trunk kde4]
| String freeze in effect
|
|-
| KPager
|
|
|
|
|-
| KPhotoalbum
| May 9 2009
| trunk
| trunk
| Message freeze, April 3 2009
|-
| KPlayer
|
|
|
|
|-
| KPovmodeler
| KDE release
|
|
|
|-
| KRecipes
| 2.0, date unknown
| [https://projects.kde.org/projects/extragear/utils/krecipes/repository/?rev=2.0 git 2.0]
| [http://websvn.kde.org/branches/stable/l10n-kde4/templates/messages/extragear-utils/ stable]
| GUI strings frozen, docs ''not'' frozen
|-
| KSig
|
|
|
|
|-
| [http://ktorrent.org/ KTorrent]
| 8 november 2009
| [http://websvn.kde.org/branches/stable/extragear-kde4/network/ktorrent stable kde4]
| [http://websvn.kde.org/branches/stable/l10n-kde4/templates/messages/extragear-network/ stable kde4]
| String freeze in effect
|-
| Kuickshow
|
|
|
|
|-
| Muon Suite
| Final Release: August 2012, pre-releases monthly
|
|
|
|-
| KWlan
|
|
|
|
|-
| RSIBreak
|
|
|
|
|-
| Skanlite
| KDE release
| trunk
|
|
|-
| [http://skrooge.org Skrooge]
| 2010-02-06 (version 0.6.0)
| [http://websvn.kde.org/trunk/extragear/office/skrooge trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-office/ trunk kde4]
| String freeze in effect
|-
| [http://www.kde-apps.org/content/show.php?content=29153 Yakuake]
| July 8th, 2010
| [http://websvn.kde.org/trunk/extragear/utils/yakuake/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-utils/ trunk kde4]
| String freeze started June 24th, 2010
|-
| Kile
| June 8th, 2011 (Version 2.1)
|
|
| String freeze started 23 May 2011
|-
| [http://www.krusader.org/ Krusader]
| 2.4.0-beta1 released on June 26, 2011.
| [http://websvn.kde.org/trunk/extragear/utils/krusader/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-utils/ trunk kde4]
| String freeze since June 26, 2011 until 2.4.0 release.
|-
| BlueDevil
| 1.0.5 (stable) and 1.1.1 (trunk) released planned on July 15, 2011.
|
| stable, trunk
| String freeze since June 29, 2011 until 1.0.5 and 1.1.1 releases.
|-
| [http://amarok.kde.org Amarok]
| July 22, 2011 (Amarok 2.4.2)
| git master
| git master
| string freeze: July 4, 2011 — July 22, 2011
|-
| [http://digikam.org digiKam]
| July 27th 2011 [http://www.digikam.org/drupal/about/releaseplan]
| [https://projects.kde.org/projects/extragear/graphics git master]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-graphics/ trunk kde4]
| String freeze starting June 30th 2011.
|-
| [http://techbase.kde.org/Projects/KMyMoney KMyMoney]
| 4.6.1 from Stable around November 5th, 2011
| [http://websvn.kde.org/trunk/extragear/office/kmymoney/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-office/ trunk kde4]
| String freeze started October 22nd, 2011
|-
| massif-visualizer
| 0.3 is planned to be released on September 4, 2011
|
|
| String freeze started on August 8, 2011
|-
| [http://tellico-project.org Tellico]
| 2.3.4
| [http://websvn.kde.org/trunk/extragear/office/tellico/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-office/ trunk kde4]
| String freeze: September 5th, 2011 -- September 18th, 2011.
|-
| [http://www.rekonq.sourceforge.net rekonq]
| ~ October 11, 2011 (Version 0.8)
| [http://gitorious.org/rekonq/mainline/trees/master git master]
| [http://gitorious.org/rekonq/mainline/trees/master git master]
| String freeze for 3 weeks starting September 21, 2011 (0.8 release)
|-
| KDE Telepathy
| November 18th, 2011 (version 0.2)
|
|
| String freeze starting October 26th, 2011.
|-
| Calligra
| After November 23th, 2011 [http://mail.kde.org/pipermail/calligra-devel/2011-July/001957.html schedule]
|
|
| String freeze starting October 12th, 2011.
|-
| [http://konversation.kde.org Konversation]
| In the first week of December, 2011
| [http://gitorious.org/konversation/konversation/trees/master git master]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-network/ trunk kde4]
| String freeze started on November 17th, 2011.
|-
| Wicd Client KDE
| 17th of December, 2011 (version 0.3)
|
|
| String freeze started on December 6th, 2011.
|}

Schedules/Extragear

2012-08-14T20:04:14Z

Nicolás: Update information about KRecipes

This page is intended to be a central location for Extragear projects to keep users and contributors (translators, packagers, etc.) informed about upcoming releases in a very accessible way.

 

{| border="1"
|-
! Project
! Next release (roughly)
! Next Release Code branch
! Next Release Translation branch
! Comments
|-
| K3b
| 1 March 2010
| [http://websvn.kde.org/trunk/extragear/multimedia/k3b/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-multimedia/ trunk kde4]
| String freeze starting from January 31 2010 (in effect)
|-
| KAudiocreator
|
|
|
|
|-
| Kaffeine
|
|
|
|
|-
| [http://extragear.kde.org/apps/kcoloredit/ KColorEdit]
| KDE release
| [http://websvn.kde.org/trunk/extragear/graphics/kcoloredit/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-graphics/ trunk kde4]
|
|-
| [http://www.kde-apps.org/content/show.php/KDE+Partition+Manager?content=89595 KDE Partition Manager]
| Q2/2010
| [http://websvn.kde.org/trunk/extragear/sysadmin/partitionmanager/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-sysadmin/ trunk kde4]
| 
|
|-
| [http://ww.kdevelop.org KDevelop]
| 1 May 2010
| [http://websvn.kde.org/trunk/extragear/sdk/kdevelop/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-sdk/ trunk kde4]
| string freeze starting 31 March 2010
|-
| KDiff3
| January 31, 2009
| [http://websvn.kde.org/trunk/extragear/utils/kdiff3/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-utils/ trunk kde4]
|
|-
| KFax
| KDE release
|
|
|
|-
| KFTPGrabber
|
|
|
|
|-
| KGrab
| KDE release
|
|
|
|-
| [http://extragear.kde.org/apps/kgraphviewer/ KGraphViewer]
| KDE release
| [http://websvn.kde.org/trunk/extragear/graphics/kgraphviewer/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-graphics/ trunk kde4]
|
|-
| KIconedit
| KDE release
|
|
|
|-
| [http://www.kmldonkey.org KMLDonkey]
| KDE release
| [http://websvn.kde.org/trunk/extragear/network/kmldonkey/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-network/ trunk kde4]
|
|-
| KNemo
| January 17, 2010
| [http://websvn.kde.org/trunk/extragear/network/knemo/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-network/ trunk kde4]
| String freeze in effect
|
|-
| KPager
|
|
|
|
|-
| KPhotoalbum
| May 9 2009
| trunk
| trunk
| Message freeze, April 3 2009
|-
| KPlayer
|
|
|
|
|-
| KPovmodeler
| KDE release
|
|
|
|-
| KRecipes
| 2.0, date unknown
| [https://projects.kde.org/projects/extragear/utils/krecipes/repository/?rev=2.0 git 2.0]
| [http://websvn.kde.org/branches/stable/l10n-kde4/ stable]
| GUI strings frozen, docs ''not'' frozen
|-
| KSig
|
|
|
|
|-
| [http://ktorrent.org/ KTorrent]
| 8 november 2009
| [http://websvn.kde.org/branches/stable/extragear-kde4/network/ktorrent stable kde4]
| [http://websvn.kde.org/branches/stable/l10n-kde4/templates/messages/extragear-network/ stable kde4]
| String freeze in effect
|-
| Kuickshow
|
|
|
|
|-
| Muon Suite
| Final Release: August 2012, pre-releases monthly
|
|
|
|-
| KWlan
|
|
|
|
|-
| RSIBreak
|
|
|
|
|-
| Skanlite
| KDE release
| trunk
|
|
|-
| [http://skrooge.org Skrooge]
| 2010-02-06 (version 0.6.0)
| [http://websvn.kde.org/trunk/extragear/office/skrooge trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-office/ trunk kde4]
| String freeze in effect
|-
| [http://www.kde-apps.org/content/show.php?content=29153 Yakuake]
| July 8th, 2010
| [http://websvn.kde.org/trunk/extragear/utils/yakuake/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-utils/ trunk kde4]
| String freeze started June 24th, 2010
|-
| Kile
| June 8th, 2011 (Version 2.1)
|
|
| String freeze started 23 May 2011
|-
| [http://www.krusader.org/ Krusader]
| 2.4.0-beta1 released on June 26, 2011.
| [http://websvn.kde.org/trunk/extragear/utils/krusader/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-utils/ trunk kde4]
| String freeze since June 26, 2011 until 2.4.0 release.
|-
| BlueDevil
| 1.0.5 (stable) and 1.1.1 (trunk) released planned on July 15, 2011.
|
| stable, trunk
| String freeze since June 29, 2011 until 1.0.5 and 1.1.1 releases.
|-
| [http://amarok.kde.org Amarok]
| July 22, 2011 (Amarok 2.4.2)
| git master
| git master
| string freeze: July 4, 2011 — July 22, 2011
|-
| [http://digikam.org digiKam]
| July 27th 2011 [http://www.digikam.org/drupal/about/releaseplan]
| [https://projects.kde.org/projects/extragear/graphics git master]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-graphics/ trunk kde4]
| String freeze starting June 30th 2011.
|-
| [http://techbase.kde.org/Projects/KMyMoney KMyMoney]
| 4.6.1 from Stable around November 5th, 2011
| [http://websvn.kde.org/trunk/extragear/office/kmymoney/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-office/ trunk kde4]
| String freeze started October 22nd, 2011
|-
| massif-visualizer
| 0.3 is planned to be released on September 4, 2011
|
|
| String freeze started on August 8, 2011
|-
| [http://tellico-project.org Tellico]
| 2.3.4
| [http://websvn.kde.org/trunk/extragear/office/tellico/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-office/ trunk kde4]
| String freeze: September 5th, 2011 -- September 18th, 2011.
|-
| [http://www.rekonq.sourceforge.net rekonq]
| ~ October 11, 2011 (Version 0.8)
| [http://gitorious.org/rekonq/mainline/trees/master git master]
| [http://gitorious.org/rekonq/mainline/trees/master git master]
| String freeze for 3 weeks starting September 21, 2011 (0.8 release)
|-
| KDE Telepathy
| November 18th, 2011 (version 0.2)
|
|
| String freeze starting October 26th, 2011.
|-
| Calligra
| After November 23th, 2011 [http://mail.kde.org/pipermail/calligra-devel/2011-July/001957.html schedule]
|
|
| String freeze starting October 12th, 2011.
|-
| [http://konversation.kde.org Konversation]
| In the first week of December, 2011
| [http://gitorious.org/konversation/konversation/trees/master git master]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-network/ trunk kde4]
| String freeze started on November 17th, 2011.
|-
| Wicd Client KDE
| 17th of December, 2011 (version 0.3)
|
|
| String freeze started on December 6th, 2011.
|}