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

List:       kde-release-team
Subject:    Re: Kate App/Part/KWrite => kate.git
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2011-01-29 14:45:07
Message-ID: 201101291445.07423.aacid () kde ! org
[Download RAW message or body]

A Dissabte, 29 de gener de 2011, Christoph Cullmann va escriure:
> On Saturday 29 January 2011 15:06:32 Albert Astals Cid wrote:
> > > And I don't see this as a special wish, given for example kdesdk will
> > > for sure split anyway up, why is it a problem if kate splits out
> > > first? How will other split modules be handled? I have no problem if
> > > kate stays in the "kdesdk" group, if there is any or any other
> > > toplevel group. I not insist on some toplevel "kate whatever" thing,
> > > just a place where the kate.git can be and be packaged with the KDE
> > > release.
> > 
> > Ok, misunderstanding from my side then, having kate.git inside extragear-
> > devtools or maybe kde-runtime (since it provides kwrite and katepart that
> > for  me are "basics" especially katepart) totally works for me (and my
> > l10n concern is vanished)
> :
> :) Where would I need to move the doc/(kwrite kate) folders in the kate.git
> 
> layout to have that working? Atm they are still in kdesdk/base.

A doc/ folder inside the kate.git root.

Albert

> 
> Greetings
> Christoph
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
[prev in list] [next in list] [prev in thread] [next in thread]