On Thursday 8. July 2010 20.14.47 Maciej Mrozowski wrote: > Right. But those users who will go through this exact same procedure over > and over AGAIN. Because: > - they weren't told Qt-4.6.2 is broken in this regard (why would they? they > just grab packages and build from source against whatever Qt version they > happen to have)
They don't HAVE to be told. Just keep upgrading everything.
You're upgrading KDE? Make sure you have the latest of its dependencies. Then
keep upgrading.
> or
> - packager who prepared packages for them was not told Qt-4.6.2 is broken
> in this regard.
Then packager is not doing his/her job. Packager should be packaging Qt 4.6.3
when it is released, regardless of whether it fixes an important KDE bug or
not.
> So the only reliable way for them to find out is to personally experience
> bug, fill it (or seach bugzilla first), then be told to go away and
> complain elsewhere (usually distro).
No, the way for them is to do their job properly.
The point of not requiring a change in KDE is because people are supposed to
upgrade without us having to tell them.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
