Please package following class http://doc.qt.digia.com/solutions/4/qtsingleapplication/index.html it is bundled in many package in the tree. Also Fedora already is using a seperate package. I didn't tried yet, because I have no clue about the qt4-build.eclass so I think it is easier for you. There are many patches available from fedora, so packing should be easy. Thanks
The plan is to start unbundling it from every package?
(In reply to comment #1) > The plan is to start unbundling it from every package? that's the plan. The gentoo way. I would do it in texmaker and texstudio. At least those packages bundle it * app-emulation/q4wine * media-sound/musescore * app-text/cb2bib * dev-util/qt-creator * net-p2p/qbittorrent * media-video/smplayer * sci-electronics/plcedit * app-editors/focuswriter * x11-misc/qlipper * media-video/minitube * media-sound/clementine * net-news/quiterss * media-sound/musique * app-text/qgoogletranslator * www-client/qupzilla * app-text/goldendict
Shouldn't we just let upstream folks to rework their build systems first? I believe this is not an urgent issue
(In reply to comment #3) > Shouldn't we just let upstream folks to rework their build systems first? I > believe this is not an urgent issue qt? sure. I just thought this one might be worth the unbundling efforts.
(In reply to comment #4) > (In reply to comment #3) > > Shouldn't we just let upstream folks to rework their build systems first? I > > believe this is not an urgent issue > > qt? sure. I just thought this one might be worth the unbundling efforts. No I meant the upstream of each package that you listed above. If Qt upstream is pushing towards this way, then we can wait until all upstreams pick up the changes
(In reply to comment #3) > Shouldn't we just let upstream folks to rework their build systems first? I > believe this is not an urgent issue Asking upstreams to unbundle it is kind of pointless if we don't offer it as a separate package. I agree we should package this, and then request the various upstreams to make it possible to compile their packages against system qtsingleapplication.
is there a release tarball available anywhere?
http://get.qt.nokia.com/qt/solutions/lgpl/
Added an initial ebuild to the qt overlay, tested against media-video/minitube. If it meets your needs we will push to portage.
Thanks, I will try it.
It seems that qtlockdfile is bundled fedora has patches to unbundle it. http://pkgs.fedoraproject.org/cgit/qtlockedfile.git/tree/
(In reply to comment #11) > It seems that qtlockdfile is bundled > > fedora has patches to unbundle it. > > http://pkgs.fedoraproject.org/cgit/qtlockedfile.git/tree/ Pushed a couple of quick commits to the overlay to fix this.
Builds fine, but texmaker needs some ancient version with functionality removed now.
I am almost finished with packaging this, but have run into a small issue. Other distributions seem to install it to /usr/include/QtSolutions/, but using this .prf it is searching /usr/include/qt4/QtSolutions qtlockedfile.prf INCLUDEPATH *= $$QMAKE_INCDIR_QT/QtSolutions DEPENDPATH *= $$QMAKE_INCDIR_QT/QtSolutions LIBS *= -lQtSolutions_LockedFile-2.4 Any ideas on which is correct?
(In reply to Michael Palimaka (kensington) from comment #14) > I am almost finished with packaging this, but have run into a small issue. > Other distributions seem to install it to /usr/include/QtSolutions/, but > using this .prf it is searching /usr/include/qt4/QtSolutions Maybe that's because in other distributions QMAKE_INCDIR_QT == /usr/include ? Btw, what's the canonical SRC_URI for the package now? get.qt.nokia.com seems to be dead.
Anyway, /usr/include/qt4/QtSolutions makes more sense to me (given our current layout), as long as it's consistent with the actual location of the header files ;)
(In reply to Davide Pesavento from comment #15) > Btw, what's the canonical SRC_URI for the package now? get.qt.nokia.com > seems to be dead. I could not find any. :( (In reply to Davide Pesavento from comment #16) > Anyway, /usr/include/qt4/QtSolutions makes more sense to me (given our > current layout), as long as it's consistent with the actual location of the > header files ;) Thanks for the info, I'll do that then.
Thanks, both qtlockedfile and qtsingleapplication are now in CVS.
Please add ~x86 keyword.
(In reply to Nikoli from comment #19) > Please add ~x86 keyword. There is already bug #483618 for that.