Why modules? (was: Re: A humble packager's request: Retire kdeaddons.)

[David Faure]

On Thursday 12 February 2004 12:31, Clarence Dang wrote:
> On Thu, 12 Feb 2004 10:05 pm, Rob Kaper wrote:
> > On Wed, Feb 11, 2004 at 10:19:57AM -0600, Russell Miller wrote:
> > > Why do we have modules at all?
> >
> > So that developers and early adopters won't have to check out several
> > gigabytes of kdepim+kdenetwork+kdegraphics when they just want
> > libs+base+games+multimedia.
> But it's possible even with one big module (not that I'm saying that it's a 
> good idea):
> 
> cvs co -l the_one_big_module
> cvs co the_one_big_module/app1
> cvs co the_one_big_module/app2

I don't want to even think about the strain on the server when people do
"cvs update" from the toplevel of the big module. It'd die every time for sure.
It's also more complex to do it correctly than currently.
This is simply not an option with CVS. Not that I want to create a thread on the
other versioning systems out there, but... :)

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