Re: k3b replaces gnomebaker?

[Jean-Philippe Guillemin <jp.guillemin@xxxxxxx>]

Selon Sebastian Reisse <sebastian.j.reisse@xxxxxxx>:

> And I remember what JP said, when gnomebaker replaced graveman and some
> asked to use k3b instead: "This won't happen until I decide to make KDE
> thze default DE in Zenwalk".

Maybe KDE is a possibility for Zenwalk. For the moment it is only a supported
toolkit for Zenwalk 5.0.

> So why he is changing his mind now?

Because only narrow-minded people don't change their opinion when it's clear
that they should.

> ZW should keep small footprint and k3b requires the half KDE, that is what
> pisses me on! ZW goes bloat!

I will take care of this if you don't mind. You will notice performance
improvement in Zenwalk 5.0, as usual.

>
> In top of that yopu also compile some other stuff with qt-support, e.g.
>
>
> [l] Updated gtk-engines-2.10.2-i486-48.2.tgz (added QTCurve)

Irrelevant : it seems that you don't know what QtCurves is...

>
> Which makes it impossible to remove kdelibs/base and qt without the need
> to rebuild all those packages having qt-support enabled.
> This makes ZW even mor bloated and gives the user less flexibility.
>
> ZenWalk is called _ZEN_ because it should have a small footprint and is
> not bloated, adding any kde stuff to the ISO makes it less _ZEN_.
> k3b is in the expra and can easyly installed so there is no need to
> recompile half ZW for those who want a qt-free tiny system.

Please stop discussing every new feature we put in the SNAPSHOT. I'm not
supposed to justify anything I do. Going on this way will only result in my
un-subscription from the Zenwalk-main ML.

End of discussion

JP