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

List:       kde-core-devel
Subject:    Re: RFC: kdenonbeta reorganisation
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2004-09-18 17:10:13
Message-ID: 200409181910.18630 () erwin ! ingo-kloecker ! de
[Download RAW message or body]


On Friday 17 September 2004 15:00, Cornelius Schumacher wrote:
> On Friday 17 September 2004 12:38, Waldo Bastian wrote:
> > To make it more accessable and better
> > maintainable, I would like to propose to split kdenonbeta in the
> > following modules:
> >
> > 1) kdeplayground-1, kdeplayground-2, ..., kdeplayground-N
> >
> > 2) kdereview-1, kdereview-2, ..., kdereview-N
>
> I don't like the moving around of projects in CVS involved with this
> organization (e.g. a project starting in the playground then being
> moved to the review module and finally being moved to a core module).
>
> I also don't like the splitting up in N modules. Partial checkouts of
> kdenonbeta work very well for me. What aspect of managability do you
> want to address by the split-up?

I might be wrong but from the time it takes to do a 'cvs up' in kdelibs 
compared with the time it takes for a much smaller cvs module I'd say 
(Warning: Uneducated guess) the load on the cvs server would be less if 
the modules are smaller. Partial checkouts work for you and me and 
would work for everybody else. But people with 160 GB hard disks will 
probably always make a complete checkout although they only need one or 
two apps.

If splitting up is nonsense then why are there several kdeextragear 
modules?

Regards,
Ingo

[Attachment #3 (application/pgp-signature)]

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

Configure | About | News | Add a list | Sponsored by KoreLogic