On 9/2/11 11:24 PM, "ext Richard Moore" <[email protected]> wrote:
>On Fri, Sep 2, 2011 at 10:06 PM, Olivier Goffart <[email protected]> >wrote: >> On Friday 02 September 2011 21:02:15 Richard Moore wrote: >>> TBH it seems to me that is is too much stuff for QtBase, a javascript >>> interpreter??!. Base implies a minimal set. For example, I'd expect to >>> be able to use qtbase to build a daemon for a headless server. I'm >>> thinking core stuff like QCoreApplication, QString possibly even the >>> networking modules. >>> >>> Right now we don't have a forum to discuss this properly, so this list >>> appears to be the best we've got. >> >> Do not mix qtbase and QtCore. >> QtBase is a repository that contains few library such as QtCore, QtGui, >> and >> now, V8. >> Considering that we plan to have both QtDeclarative, QtWebKit, and the >> replacement for QtScript that are going to use V8, it make sens to put >> this >> common dependence in qtbase. >> >> When you do your minimal deamon, you can just link against QtCore, you >>do >> not >> need V8. (you do not even need to compile it, you can pass -no-v8) >> >> I hope this answer your concern. > >I'm afraid not. Once the code is packaged we'll end up with a qt-base >rpm, this will have the dependencies of everything in the qtbase >repository. That means that if someone wants to install my daemon >they'll end up pulling in everything else. The alternative would be to >have the same repo packaged multiple times with various options which >will lead to problems, for example the possibility of multiple qt-base >packages that are incompatible due to different options/feature sets. That's not true today neither. Qt 4.x is usually packaged as a long list of rpm/debs on all Linux distributions I know. Even if qtbase is one repository, this doesn't mean it can't be several binary packages. And who said the current state of qtbase is the final one? Long term I want to split up the repository further. But even if you have the dependency, I don't see the problem. Currently QtCore also links against glib. Do you use any of it for your daemon? Probably not, still nobody ever complained about it. > >This problem can be avoided completely by simply having another module. > >The wider problem is the total lack of discussion on any public forum. >This is a much more important issue, and one that is currently being >handled terribly by the Qt team. I think people have been fairly >patient about the lack of opengov so far, but since we've now passed >the date given at QCS as being the Qt 5.0 feature freeze, it's time to >demonstrate that this is more than hot air. I am as frustrated as you about it not being out yet (and so are many people inside Nokia). While I can't tell you details of why this takes so long, I can assure you that this was in this case not really Nokia's fault. Cheers, Lars _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
