[Kde-extra-gear] backwards compatibility

[Klas Kalass]

Am Mittwoch, 28. Januar 2004 00:04 schrieb Joachim Eibl:
> 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
And for everybody else building just fails. The purpose of configure is that 
building does not fail, but rather problems are pointed out at configure 
time. I rather add a note to the README.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
Url : http://mail.kde.org/pipermail/kde-extra-gear/attachments/20040201/77785e4c/attachment.pgp