<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<title></title></head>
<body>
<p>----- Original message -----
<br>> Hi,
<br>>
<br>> we are working on digikam's git migration and would like to migrate soon.
<br>> The problem is our interdependency with libkexiv2, libkdcraw and libkipi
<br>> from  kdegraphics/libs. In fact, there are branches for these libs in
<br>> extragear, so  digikam cannot migrate without these libs, and the libs
<br>> cannot migrate without  digikam and related branches.
<br>>
<br>> Btw, it seems pretty obvious that kdegraphics will end up in split
<br>> repos.  There are separate applications in there.
<br>> And <a href="mailto:kde-graphics-devel@kde.org">kde-graphics-devel@kde.org</a> is deserted, no answers there.
<br>>
<br>> Questions:
<br>> 1) Are there plans for kdegraphics migration?
<br>No.
<br>
<br>> 2) Assume noone has plans and rules for the full module. Is it
<br>> acceptable to  migrate kdegraphics/libs before?
<br>
<br>Why not migrate the rest of the module too?
<br>
<br>If kde-graphics-devel isn't answering, I would reccomend looking at the list of apps in kdegraphics and post to their respective lists or direct to their maintainers. Kde-scm-interest is for helping each other in the process of conversion, its not some final arbitrator. So like "Kdebase/apps" doesn't have a mailing list either, so I just mailed several relevant people directly.
<br>
<br>Also I don't see why some libraries you depend on being in another SCM is an issue.
<br>
<br>Ian</p>
</body>
</html>