[kde-freebsd] Qt 5

[Max Brazhnikov]

On Wed, 5 Dec 2012 01:46:57 +0100, Alberto Villa wrote:
> On Fri, Nov 16, 2012 at 12:25 AM, Max Brazhnikov <makc at issp.ac.ru> wrote:
> > 2) iconengines, imageformats, inputmethods could be merged into qt-runtime
> 
> This is a bit tricky, because of splitted tarballs. Here is what I plan to do:
> - install ICO, JPEG and GIF imageformats along with qt5-gui (only
> added dependency is libjpeg);
> - install inputmethods (which I suppose is now platforminputcontexts)
> along with qt5-gui (no additional dependency);
> - install SVG imageformat and iconengine along with qt5-svg (as per
> tarball layout);
> - create a qt5-imageformats port for additional plugins (which have
> their own tarball).
> Does it sound good?

Great!

> As you may have seen, I've also packed PlatformSupport and generic/XCB
> platform plugins with qt5-gui; that's because qt5-gui won't work
> without one of them (XCB to be the preferred one), but since they
> depend on qt5-gui they can't be made a dependency of it. Another
> solution could be to split the XCB plugin (the only one with
> additional dependencies) and make the Qt "gui" component install it
> too; it would let people depend only on qt5-gui, but I don't like it.
> I don't think we can expect people to install the plugin on their own
> (a'-la Phonon), in which case stuff like kde-workspace should depend
> on it; not easy, I think.
> 
> Similar situation for PrintSupport: I didn't split CUPS plugin in its
> own port for the same reason, but rather made it optional at
> buildtime.
> 
> What's your opinion on these matters?

I'm fine with either solution, buildtime options seem quite reasonable.
 
> > 4) qmake-based projects are quite popular, I'm thinking about QMAKE_CONFIGURE,
> > which will invoke 'do-configure' like editors/texmaker does.
> 
> How do USE_QMAKE=[45], QMAKE_ENV and QMAKE_ARGS (in place of
> QMAKEFLAGS) sound? To mimic CMake stuff...

All right.