Hi Gentoo-Developers, for all qt-embedded developers it's necessary to have a qvfb, the qt virtual framebuffer. it's a X11 application that simualtes a framebuffer device. for compiling this qt must configured with -qvfb for that you can add a new USE variable named qvfb? when it's set, the qt virtual framebuffer ist compiled with qt-x11. tia ar
The qt-embedded ebuild builds a qt with -qvfb.
I'm reopening this bug because we missed something: to make qvfb work one needs qt-embedded compiled with -qvfb (and that's ok) and the qvfb tool from standard qt. qvfb is not compiled by default in qt, so to fulfill the request we should add a snippet similar to the one for bug 91666 to run make in the tools/qvfb directory (conditional on a USE flag? the overhead of the qvfb binary is ~130kB).
Created attachment 77668 [details] ebuild containing qvfb USE flag Here's an ebuild that I modified for qt-3.3.4-r8 that adds a qvfb USE flag and it does compile and install qvfb. Hope it helps...
*** Bug 152556 has been marked as a duplicate of this bug. ***
Created attachment 112143 [details] x11-misc/qvfb-3.3.4.ebuild Another approach: make it a separate ebuild. I'd rather this approach because qvfb doesn't have anything to do with the rest of qt-embedded package.
Please remove the empty RDEPEND assignment from the ebuild before using it
(In reply to comment #6) > Please remove the empty RDEPEND assignment from the ebuild before using it shouldn't it be something like RDEPEND="${DEPEND}"?
(In reply to comment #7) > (In reply to comment #6) > > Please remove the empty RDEPEND assignment from the ebuild before using it > > shouldn't it be something like RDEPEND="${DEPEND}"? > According to `man 5 ebuild`, RDEPEND should be set automatically as same as DEPEND if not set.
Created attachment 162897 [details] dev-embedded/qvfb-4.4.1.ebuild New ebuild based on the split Qt-4.4 ebuilds. I've been maintaining qvfb (and Qt Embedded) for several years now and are willing to maintain this ebuild if help is wanted/needed.
Created attachment 187739 [details] Simplified qvfb ebuild for qt-4.5.0.
Ok it has been ages, but now qt is willing to take care of this package. Tais, are you interested in proxy-maintain this package cause we dont have the means to test it ? Thanks
I've tested the ebuild against 4.5.1 and it seems to work fine. If Tais are unable to do proxy-maintenance I could be willing to step up. As mentioned in comment #9 I know qvfb, qt and qt-embedded fairly well (I guess I could also join the qt herd if you need more people).
(In reply to comment #12) > I've tested the ebuild against 4.5.1 and it seems to work fine. If Tais are > unable to do proxy-maintenance I could be willing to step up. As mentioned in > comment #9 I know qvfb, qt and qt-embedded fairly well (I guess I could also > join the qt herd if you need more people). > Well, you can be both proxy maintainers. I ll add you as proxy maintainer for now and later we can add Tais. First of all, I will fix the ebuild as it has some mistakes. I ll put it on qting-edge overlay at first for some clean up and I ll push it to portage within the next 3 days New people are always welcomend in Qt herd but you need to follow the standard recruitment process first[1] if you really want to become dev :) [1]: http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2
I ve added the following ebuilds on qting-edge overlay *qvfb-4.5.1 *qvfb-4.5.9999 *qvfb-4.9999 As I said before, 4.5.1 will stay there for 3 days for further testing :)
I've tested the ebuild in the qting-edge overlay and this works equally fine. However I find the ebuild category a bit confusing. It's placed in x11-libs/qvfb but it's really not a library but a standalone application used when testing/developing qt-embedded applications. So, IMO, the ebuild should be placed in dev-embedded/qvfb.
(In reply to comment #15) > I've tested the ebuild in the qting-edge overlay and this works equally fine. > However I find the ebuild category a bit confusing. It's placed in > x11-libs/qvfb but it's really not a library but a standalone application used > when testing/developing qt-embedded applications. > > So, IMO, the ebuild should be placed in dev-embedded/qvfb. > Ok I ve changed the ebuild category :)
On tree +*qvfb-4.5.1 (26 May 2009) + + 26 May 2009; Markos Chandras <hwoarang@gentoo.org> +qvfb-4.5.1.ebuild, + +metadata.xml: + Initial commit of qvfb tool. Fixes bug 43827. Thanks to Håvard Wall + <haavardw@ifi.uio.no> and Tais M. Hansen <tais.hansen@osd.dk> for the + initial + ebuilds. + Havard, you ll be proxy maintainer for this package so ping me or any other qt member for future updates or problems concerning this package Thanks for your effort :)
