RFC: remove qt-copy

[Olivier Goffart]

Le Mandag 25 mai 2009, Aaron J. Seigo a écrit :
> Thoughts? Opinions?

It is maybe the time to redefine what's qt-copy^W kde-qt and what's his role.

In an ideal world, everyone should just use the packaged, released Qt, just as 
we use others packaged libraries we depend on.
The reason we have qt-copy is that Qt is our biggest dependency, and a very 
important one, KDE rely on it. And it was a place for kde developer to 
publish their patches that fixes bugs that appears in KDE, or to submit 
patches from upstream that are really important for the stability of KDE, 
before a release is made.

Anyway, regarding kde-qt:
What kind of patches should go there?
What should distributions ship?

Is kde-qt like a stable branch of Qt maintained by the KDE team?

What kind of fixes should be backported from the Qt development branch to 
kde-qt?


Also, I would like to emphasis that pushing a change to qt-copy or kde-qt is 
not a good way to get it integrated into Qt. If you want your patches into 
Qt, you must do merge request.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090525/4117e014/attachment.sig>