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

List:       kde-extra-gear
Subject:    Re: [Kde-extra-gear] backwards compatibility
From:       Joachim Eibl <joachim.eibl () gmx ! de>
Date:       2004-01-27 23:04:28
Message-ID: 200401280004.28973.joachim.eibl () gmx ! de
[Download RAW message or body]

On Tuesday 27 January 2004 20:12, Klas Kalass wrote:
> Am Montag, 26. Januar 2004 17:30 schrieb George Staikos:
> > On Monday 26 January 2004 02:27, Klas Kalass wrote:
> > > > > The problem is, that the entire module cannot be compiled if there
> > > > > was a MIN_CONFIG(3.1). The occasional developer should still be
> > > > > able to check out the stuff in the extragear modules and fix
> > > > > things.....

I would have hoped that each project could have its own requirement, and only 
when compiling everything, the highest version requirement gets the priority. 
(But that's just what I think should happen.)

> As of now I see 2 solutions:

If nothing else is possible, then I also favour solution 1).

But what about a third possibility (a variant of 1) where the entire module 
uses the lowest requirement in the CVS for the entire module? People using 
the latest stable KDE from CVS won't notice the difference. And applications 
that provide extra packages can put the higher requirement into their README 
and on their respective homepages.

Joachim
_______________________________________________
Kde-extra-gear mailing list
Kde-extra-gear@kde.org
https://mail.kde.org/mailman/listinfo/kde-extra-gear
[prev in list] [next in list] [prev in thread] [next in thread]