[Kde-scm-interest] Re: Idea: Converting KDESDK incrementally

[Michael Pyne]

On Monday, March 28, 2011 22:48:11 Sebastian Dörner wrote:
> Hi,
> 
> KDESDK is still using svn up to now and there doesn't seem to be much
> progress to make the transition for the whole repository. Also see the
> brief discussion on December 18th on kde-scm-interest.
> I guess one of the reasons is that KDESDK is rather an ensemble of
> individual sub-projects than one coherent module, so there is nobody who
> knows all the code and its history (correct me if wrong). Also, as
> stated in the a. m. discussion, the current maintainer doesn't have time
> to do it.
> 
> I wonder if it would be feasible/sensible to do the conversion
> incrementally.

This has already happened, in at least one regard: kdesrc-build, which used to 
be in kdesdk/scripts, but is now separated out to extragear/utils on 
git.kde.org.

In fairness I always kind of treated it like an Extragear module (it probably 
should have been there the whole time, but I had imported the script into the 
same directory as the existing kde-build script).

> Is there anything that makes this proposal a bad idea? How does it align
> with release management?

It makes release management probably more difficult, but kdesdk would not be 
the first module to end up as multiple git repositories. On the other hand I'd 
be more interested in knowing whether the KDE SDK module maintainer would 
support moving applications piecemeal like this -- presumably the rest of 
kdesdk (besides /scripts) makes a more coherent package than kdesrc-build did 
with kdesdk.

Regards,
 - Michael Pyne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20110328/e9e156d5/attachment.sig