Redefining kdelibs and kdebase

David Faure faure at kde.org
Mon Aug 29 22:01:11 BST 2005


On Monday 29 August 2005 20:26, Nicolas Goutte wrote:
> 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/
See this? ;)

> > I would even suggest kdebase/workspace and kdebase/apps too, for the same
> > reasons. Smooth migration...
> 
> Then why not doing like the extragear and playground modules and have:
> 
> kdelibs/components
> kdelibs/framework
> kdelibs/kde3support

I think we agree - this is exactly what was suggested from the start ;-)
(Yes I agree with the removal of the "kde" prefix in the submodules, since the tarballs would
be "kdelibs-framework" and not "kdeframework").

> Each would be independant, have an admin module, would correspond to a 
> tarball, would correspond to a single generic translation file (replacements 
> of kdelibs.po).
> 
> And you could check them out with
> svn checkout kdelibs
> in one go, nevertherless...

Exactly.

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).





More information about the kde-core-devel mailing list