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

List:       kde-core-devel
Subject:    Re: Code duplication in KWrite, comment/uncomment stuff
From:       David Faure <david () mandrakesoft ! com>
Date:       2000-05-28 16:24:34
[Download RAW message or body]

On Sun, May 28, 2000 at 06:23:05PM +0200, Simon Hausmann wrote:
> 
> 
> On Sat, 27 May 2000, Ralf Nolden wrote:
> 
> > Simon Hausmann wrote:
> > > 
> > > I neither can nor want to decide on this issue :-}
> > > 
> > > There are two valid points:
> > > 
> > > - KWrite is an application. kdelibs contains *core* library stuff
> > >   Although I agree that a text editor component is indeed a core
> > >   component of a desktop environment.
> > > 
> > > - However the fact that kdevelop would depend on kdebase isn't really a
> > >   good thing either.
> > > 
> > > How about this:
> > > 
> > > We make kwrite a separate CVS module and "link" it into the kdebase and
> > > the kdevelop CVS module via CVSROOT/modules , just like kde-common/admin .
> > > 
> > > What do you think?
> > I think that would be a suitable solution. After all, itīs just to keep
> > kwrite sourcecode in sync, isnīt it ?
> 
> Yes
> 
> 
> Now we need the help of the CVS Masters :-) Coolo, David, anyone
> listening? :-)

Note that the link thing means that everyone will need to recheckout
completely kdebase to get the stuff, since cvs update doesn't do it
(for some reason).

Should I proceed ?

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://home.clara.net/faure/
KDE, Making The Future of Computing Available Today
See http://www.kde.org/kde1-and-kde2.html for how to set up KDE 2

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