From kde-core-devel Mon Sep 12 19:22:07 2005 From: Alexander Neundorf Date: Mon, 12 Sep 2005 19:22:07 +0000 To: kde-core-devel Subject: Re: Redefining kdelibs and kdebase Message-Id: <200509122122.07467.neundorf () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=112655295419100 Hi, On Sunday 28 August 2005 10:56, David Faure wrote: > On Saturday 27 August 2005 21:44, Nicolas Goutte wrote: > > > How it would look in svn: > > > kdelibs/kde3support/ > > > kdelibs/kdecomponents/ > > > kdelibs/kdeframework/ > > > > > > kdeworkspace/ > > > > > > kdebase/ > > > > > > > > > Even though componants, compat and framework are seperate packages > > > they could be in kdelibs.  So end the end we would only be making one > > > new module. > > > > If there is an effort of making a split then please show it as separate > > modules too, otherwise it is nearly useless to make this discussion. > > I am the one who suggested subdirs in kdelibs instead of three new modules. > The reason is that this way we keep the good old habit of: building KDE is > as simple as "build+install kdelibs, then compile any other KDE code you > want". Everyone is used to that, and if we change to "build+install three > modules", anyone who is not reading this discussion will be completely lost > as to how to build KDE. The idea is that release this code as three > tarballs though, > kdelibs-components (*) > kdelibs-framework > kdelibs-kde3support Just coming back from my 3-week vacation (which was the reason I couldn't attend akademy) I have to say this sounds very nice. We discussed this topic already several times during the KDE 3 lifecycle and now it finally comes true :-) > (and kdelibs-workspace IMHO, for workspace libs; libs for kicker applets, > screensavers etc.) I wouldn't put these libs under kdelibs/ since they belong to the "workspace". Bye Alex -- Work: alexander.neundorf@jenoptik.com - http://www.jenoptik-los.de Home: neundorf@kde.org - http://www.kde.org alex@neundorf.net - http://www.neundorf.net