[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: branches/work/kdepim-3.5.5+
From:       "Friedrich W. H. Kossebau" <kossebau () kde ! org>
Date:       2007-02-28 15:16:31
Message-ID: 200702281616.32806.kossebau () kde ! org
[Download RAW message or body]

Am Mittwoch, 28. Februar 2007 15:09, schrieben Sie:
> Friedrich W. H. Kossebau wrote:
> > fetch khalkhi from anonsvn, so anonsvn users have no problems
> 
> svn+ssh users too.

Alright. :)

Added an entry with my understandings to the TechBase, please correct things 
there if something is wrong:
http://techbase.kde.org/Getting_Started/Sources/Using_Subversion_with_KDE#Linking_in_subdirectories_from_other_branches


Friedrich

--- 8< ---
== Linking in subdirectories from other branches ==

It can happen you would like to include a copy of a subdirectory in another 
branch, 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 is still 
a 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>.

A special case is the subdirectory <tt>admin</tt>, containing the KDE build 
utilities. It is linked in to the top directory in all modules, and developed 
in <tt>/trunk/KDE/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/trunk/KDE/kde-common/admin
there is no need to change this.
--- 8< ---


[prev in list] [next in list] [prev in thread] [next in thread]