[Kde-extra-gear] backwards compatibility

[Klas Kalass]

Am Montag, 26. Januar 2004 17:40 schrieb Jesper K. Pedersen:
> Klas Kalass <klas.kalass at 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?
>
> Maybe I'm stating the obvious here, but couldn't we just move around, so
> those requiring 3.2 would be in say kdeextragear-3 (That doesn't exists
> yet, does it?)
That would mean that applications in the extra gear would be shuffled around 
whenever a maintainer wants to use a newer KDE version for his/her app.
I don't like that because noone should have to check all the modules just to
find out where his/her favourite app went.

Regards,
  Klas