RFC: remove qt-copy

[Aaron J. Seigo]

On Tuesday 26 May 2009, Matthew Woehlke wrote:
> Aaron J. Seigo wrote:
> > On Tuesday 26 May 2009, Thiago Macieira wrote:
> >> I'm with Sune here.
> >
> > that every distro should ship a differently patched Qt at the
> > discretion of the packager?
>
> To play a bit of Devil's Advocate... if you're against this, I hope
> you're against distros patching *anything*. Otherwise, what makes Qt
> special?

patching apache's http or a linux kernel driver is rather different than 
changing how a library that 1000s of third parties expect to work in a 
reliably consistent manner.

what makes Qt "special" (along with similarly placed libraries and shared 
infrastructure bits) is this shared usage, particularly as we ought to play 
nicely with other users of Qt. 

i've heard quite a bit from such groups, both free and non-free product teams, 
over the years about how much this situation _sucks_ for them and makes them 
distrust Qt-on-Linux.

the same is true of any piece of infrastructure that is so widely shared. it's 
a PITA when dealing with x.org that works differently on different OSes, too, 
for instance. (though that's not a distro issue)

> > * best is to just work directly with Qt upstream and stop this whole
> > "having patches floating forever in qt-copy"
>
> +100 to that :-). (Isn't that part of what we're trying to achieve,
> anyway?)

i think so. or at least hope so. :)

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Software

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090526/a8ae00f8/attachment.sig>