Bug#437354: libqt4-dev: Put qmake into its own package
Sune Vuorela <firstname.lastname@example.org> writes:
> On Tuesday 12 February 2008, Brian Nelson wrote:
>> Evgeni Golov <email@example.com> writes:
>> > Hi,
>> > are there any updates on this? I maintain pokerth which needs qmake4,
>> > libqt4-core and libqt4-gui, but not -sql, -qt3support etc.
>> > At the moment it build-depends on libqt4-dev which fetches way too much
>> > stuff in during building, what is annoying :)
>> I don't see any compelling reason to split out qmake, and doing so now
>> would probably break some package builds. I think this should be closed
>> or tagged wontfix.
> Some of us are talking about reorganizing how qt4 is packaged. for example,
> libQtCore is quite nice for all sorts of things locally, but you can't
> install that on debian without pulling all sorts of other things in.
I think it would be reasonable to put each library in a separate
package. When I first packaged Qt4, there was nothing out there using
just, e.g. libQtCore, without using other parts of Qt, so it seemed
wasteful to split everything up. That's probably no longer the case.
> The dev package has not yet been discussed, but it might be possible to do
> something at the same time.
When it comes to -dev packages, the more things are split up the more
users get confused IMO. When a user installs libqt4-dev, I think
they'll usually think they're getting the full Qt4 development
environment. We could have libqt4-dev pull in e.g. qt4-qmake or
whatever, but I think that would be catering to such a tiny niche that
it wouldn't be worth the package bloat.
Plus, qmake is a shitty build tool and I'd rather not encourage its use
by splitting it out of libqt4-dev. :P
Captain Logic is not steering this tugboat.