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

List:       kde-extra-gear
Subject:    Re: [Kde-extra-gear] backwards compatibility
From:       Klas Kalass <klas.kalass () gmx ! de>
Date:       2004-01-25 18:57:40
Message-ID: 200401251957.52633.klas.kalass () gmx ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Am Sonntag, 25. Januar 2004 19:51 schrieb Jesper K. Pedersen:
> Klas Kalass <klas.kalass@gmx.de> writes:
> | Hi all,
> |
> | it was brought to my attention that there arises a problem with some
> | applications requiring an up-to date version of KDE and thus needing
> | MIN_CONFIG(3.2) in the configure file, unfortunately this means
> | that everybody who wants to stay backwards compatible needs to make sure
> | by themselves to change configure.in.in locally prior to a release.
> | Otherwise your packages will require KDE 3.2.
> |
> | Any ideas how we can handle this more elegantly?
>
> If no other solutions was found, wouldn't it be better that those needing
> 3.2 was doing the editing - if for nothing else, they would be the persons
> who was mostly aware of the issues.
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.....


Klas

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

_______________________________________________
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]