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

List:       kde-core-devel
Subject:    Re: Where to put post-2.2 development
From:       Cristian Tibirna <tibirna () kde ! org>
Date:       2001-09-24 1:38:32
[Download RAW message or body]

On Sunday 23 September 2001 19:52, Charles Samuels wrote:
> On Sunday, Neil Stevens wrote:
> > On Sunday September 23, 2001 02:31, Charles Samuels wrote:
> > > I think in programs like Noatun (and Kate?), no commits of plugins need
> > > to be made.  Just keep them locally and release them yourself.  IMO,
> > > another Noatun 1.x release is a bad idea, especially when it's not part
> > > of a larger release.
> >
> > So what's the point of having a CVS?  Is it a glorified FTP repository?
>
> You're free to make a branch, it'l just never be part of an actual KDE
> release.  You'll have to put out your own tarballs.

Well, this is a little bit too radical. Never say never.

Anyways, all this discussion was already purported many times. It is visible 
that the rather strict policy of developing KDE as an integrated environment 
is a hinder for some of the applications involved.

I always was the partisan of keeping only the very essential libs and apps as 
part of the main KDE distro. And I also know it was always expected that more 
apps (especially from the kdenetwork/kdegraphics/kdemultimedia modules) go 
their ways into independent releases, with an eventual more careful release 
sync during major KDE releases.

It is also of much importance in the matter the fact that the kde libs lost 
backwards source and binary compats many times in the last few years.

But I believe the most important thing is that maintaining a CVS constituted 
of 10-15 modules is already a herculean task. Perhaps few realize how central 
is Coolo's work to KDE's existence.

So, perhaps the discussion should go in the direction of finding solutions for 
CVS modularisation, collective CVS administration, more advanced CVS 
packaging tools (starting from the already very good kdesdk/scripts/cvs2pack) 
and so on.

Thanks for listening

CT¨½jA{xRÀ/‚A°¢U0‚Aø@P¡RH¹A@

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