[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-scm-interest
Subject: [Kde-scm-interest] Re: kdegraphics libs migration
From: Ian Monroe <ian.monroe () gmail ! com>
Date: 2010-12-27 23:13:24
Message-ID: 1293491604.1438.6.camel () tekka2
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
----- Original message -----
> Hi,
>
> we are working on digikam's git migration and would like to migrate soon.
> The problem is our interdependency with libkexiv2, libkdcraw and libkipi
> from kdegraphics/libs. In fact, there are branches for these libs in
> extragear, so digikam cannot migrate without these libs, and the libs
> cannot migrate without digikam and related branches.
>
> Btw, it seems pretty obvious that kdegraphics will end up in split
> repos. There are separate applications in there.
> And kde-graphics-devel@kde.org is deserted, no answers there.
>
> Questions:
> 1) Are there plans for kdegraphics migration?
No.
> 2) Assume noone has plans and rules for the full module. Is it
> acceptable to migrate kdegraphics/libs before?
Why not migrate the rest of the module too?
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.
Also I don't see why some libraries you depend on being in another SCM is an issue.
Ian
[Attachment #5 (text/html)]
<!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>
_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic