atom feed21 messages in org.kde.kde-core-develRe: Plan to transition to KDE Frameworks
FromSent OnAttachments
David FaureJun 6, 2011 4:43 pm 
David FaureAug 6, 2011 6:31 am 
Eike HeinAug 6, 2011 6:56 am 
Michael PyneAug 6, 2011 7:09 am 
David FaureAug 6, 2011 7:52 am 
Stephen KellyAug 7, 2011 4:44 am 
Michael JansenAug 7, 2011 5:43 am 
Allen WinterAug 7, 2011 5:58 am 
Albert Astals CidAug 7, 2011 6:12 am 
Aaron J. SeigoAug 7, 2011 6:19 am 
Allen WinterAug 7, 2011 6:26 am 
Stephen KellyAug 7, 2011 6:55 am 
David FaureAug 7, 2011 7:21 am 
Stephen KellyAug 7, 2011 10:06 am 
Scott KittermanAug 7, 2011 9:42 pm 
Kevin OttensAug 8, 2011 12:27 pm 
David FaureAug 9, 2011 4:05 pm 
Scott KittermanAug 9, 2011 4:25 pm 
David FaureAug 10, 2011 5:39 am 
Scott KittermanAug 10, 2011 8:49 am 
David FaureAug 11, 2011 2:25 am 
Subject:Re: Plan to transition to KDE Frameworks
From:David Faure (fau@kde.org)
Date:Aug 6, 2011 7:52:12 am
List:org.kde.kde-core-devel

On Saturday 06 August 2011 10:10:16 Michael Pyne wrote:

If you do use prefix just make sure the path is whereever you want kdelibs (frameworks branch) to be installed.

Sure; the reason I included the line is to encourage people to install kdelibs-frameworks in a different prefix than the rest of KDE. Otherwise their KDE will break at the first BIC change. And later on when we port things like kde-runtime, we want to be able to point to a prefix that doesn't have the 'old libs'.

Side note: this is where it shows that it's also useful to have the self- compiled kdelibs dependencies (soprano, dbusmenu, and so on) in a different prefix than the rest of KDE (kdesupport_trunk in my example), to be able to use them for both master and frameworks :-)