I have make and tested a new ebuild and all other necessary files to install QSA 1.2.1 (dev-libs/qsa-1.2.1).
Created attachment 102196 [details] dev-libs/qsa/qsa-1.2.1.ebuild
Created attachment 102197 [details] dev-libs/qsa/Manifest
Created attachment 102198 [details] dev-libs/qsa/files/digest-qsa-1.2.1
Created attachment 102199 [details] dev-libs/qsa/files/qsa-1.2.1-qt4.diff
With USE editor and examples enabled a compile error for example 'console' can to appear. Call 'emerge qsa' again can fix the problem. No idea why???
Comment on attachment 102196 [details] dev-libs/qsa/qsa-1.2.1.ebuild ># Copyright 1999-2006 Gentoo Foundation ># Distributed under the terms of the GNU General Public License v2 ># $Header: $ > >inherit eutils toolchain-funcs qt4 > >S="${WORKDIR}/${PN}-x11-opensource-${PV}" > >DESCRIPTION="Qt Script for Applications, a ECMAScript based scripting toolkit for making customizable Qt/C++ applications." >SRC_URI="ftp://ftp.trolltech.com/qsa/source/${PN}-x11-opensource-${PV}.tar.gz" >HOMEPAGE="http://www.trolltech.com/" >LICENSE="GPL-2" > >SLOT="4" >KEYWORDS="~x86 ~amd64" >IUSE="debug doc examples ide editor threads" >DEPEND=">=x11-libs/qt-4.0.1" > >pkg_setup() { > QTBASEDIR=/usr/$(get_libdir)/qt4 > QTPREFIXDIR=/usr > QTBINDIR=/usr/bin > QTPCDIR=/usr/$(get_libdir)/pkgconfig > QTDOCDIR=/usr/share/doc/${PF} > QTDATADIR=/usr/share/qt4 > QTHEADERDIR=/usr/include/qt4 > QTLIBDIR=/usr/$(get_libdir)/qt4 > QTPLUGINDIR=${QTLIBDIR}/plugins > QTSYSCONFDIR=/etc/qt4 > QTTRANSDIR=${QTDATADIR}/translations > QTEXAMPLESDIR=${QTDATADIR}/examples > QTDEMOSDIR=${QTDATADIR}/demos > > PLATFORM=$(qt_mkspecs_dir) >} > >qt_mkspecs_dir() { > # Allows us to define which mkspecs dir we want to use. > local spec > > case ${CHOST} in > *-freebsd*|*-dragonfly*) > spec="freebsd" ;; > *-openbsd*) > spec="openbsd" ;; > *-netbsd*) > spec="netbsd" ;; > *-darwin*) > spec="darwin" ;; > *-linux-*|*-linux) > spec="linux" ;; > *) > die "Unknown CHOST, no platform choosed." > esac > > CXX=$(tc-getCXX) > if [[ ${CXX/g++/} != ${CXX} ]]; then > spec="${spec}-g++" > elif [[ ${CXX/icpc/} != ${CXX} ]]; then > spec="${spec}-icc" > else > die "Unknown compiler ${CXX}." > fi > > echo "${spec}" >} > >src_compile() { > if ! use ide; then > myconf="${myconf} -no-ide" > fi > > if ! use editor; then > myconf="${myconf} -no-editor" > fi if ! use debug; then myconf="${myconf} -release" fi > > # necessary because configure script use a qt3 cache > epatch ${FILESDIR}/${P}-qt4.diff > > ./configure -prefix ${QTPREFIXDIR} ${myconf} || die > > emake || die >} > >src_install() { > export PATH="${S}/bin:${PATH}" > export LD_LIBRARY_PATH="${S}/lib:${LD_LIBRARY_PATH}" > > #includes > insinto ${QTHEADERDIR} > doins src/qsa/qsaglobal.h > doins src/qsa/qsconfig.h > doins src/qsa/qsproject.h > doins src/qsa/qsinterpreter.h > doins src/qsa/qseditor.h > doins src/qsa/qsutilfactory.h > doins src/qsa/qswrapperfactory.h > doins src/qsa/qsobjectfactory.h > doins src/qsa/qsscript.h > doins src/qsa/qsinputdialogfactory.h > doins src/ide/qsworkbench.h > > #QSA mkspec feature > insinto ${QTDATADIR}/mkspecs/$(qt_mkspecs_dir) > doins src/qsa/qsa.prf > > #libs > insinto ${QTLIBDIR} > insopts -m0644 > doins lib/libqsa.so.1.2.1 > if use debug; then > doins lib/libqsa_debug.so.1.2.1 > fi > cd ${QTLIBDIR} > ln -s libqsa.so.1.2.1 libqsa.so.1.2.0 > ln -s libqsa.so.1.2.0 libqsa.so.1.2 > ln -s libqsa.so.1.2 libqsa.so.1 > ln -s libqsa.so.1 libqsa.so > if use debug; then > ln -s libqsa_debug.so.1.2.1 libqsa_debug.so.1.2.0 > ln -s libqsa_debug.so.1.2.0 libqsa_debug.so.1.2 > ln -s libqsa_debug.so.1.2 libqsa_debug.so.1 > ln -s libqsa_debug.so.1 libqsa_debug.so > fi > cd ${S} > > #documentation > if use doc; then > dohtml -A dcf -r doc/html/* > fi > > #examples > if use examples; then > insinto /usr/share/doc/${PF} > doins -r examples > fi > > dodoc README changes-1.2.1 >} > >pkg_postinst(){ > if use doc; then > #include QSA Documentation content file into assistant > ${QTBINDIR}/assistant -addContentFile ${QTDOCDIR}/html/qsa.dcf > einfo Please use "${QTBINDIR}/assistant -addContentFile ${QTDOCDIR}/html/qsa.dcf" when no QSA Help exists. > fi >} > >pkg_prerm(){ > pkg_setup > cd ${QTLIBDIR} > rm -f libqsa.so > if use debug; then > rm -f libqsa_debug.so > fi > if use doc; then > #remove QSA Documentation content file into assistant > ${QTBINDIR}/assistant -removeContentFile ${QTDOCDIR}/html/qsa.dcf > fi >}
The previously changes are for installed qt-4.2.1 which has no separate *_debug.so files. So install qsa with -debug USE flag.
In src_install(): - cd ${QTLIBDIR} + cd ${D}{QTLIBDIR} Is it not better to check if qt was built with the "debug"-flag rather than having an own? - IUSE="debug doc examples ide editor threads" + IUSE="doc examples ide editor threads" - if ! use debug; then + if ! built_with_use x11-libs/qt debug ; then
(In reply to comment #8) > Is it not better to check if qt was built with the "debug"-flag rather than > having an own? > - IUSE="debug doc examples ide editor threads" > + IUSE="doc examples ide editor threads" > > - if ! use debug; then > + if ! built_with_use x11-libs/qt debug ; then generally yes - it's better. but proposition like this is bad, bad, bad! ( ;) ) if you build qt without debug USE flag and later emerge qsa with debug USE, qsa will be build for release (and not debug). still - pkg db will store info about _used_ debug USE. this is wrong. good solution would be to make a check in pkg_setup function. there yo ucan check any prerequisite tasks. and - if user try to build qsa with debug, check is qt was build with debug, and if not - 'die' with emerge. Cheers, Przemek
I have a problem. I install whit a overlay. but when a take emerge qsa I found this error. >>> Install qsa-1.2.1 into /var/tmp/portage/dev-libs/qsa-1.2.1/image/ category dev-libs ACCESS DENIED symlink: /usr/lib64/qt4/libqsa.so.1.2.0 ln: creating symbolic link `libqsa.so.1.2.0': Permission denied ACCESS DENIED symlink: /usr/lib64/qt4/libqsa.so.1.2 ln: creating symbolic link `libqsa.so.1.2': Permission denied ACCESS DENIED symlink: /usr/lib64/qt4/libqsa.so.1 ln: creating symbolic link `libqsa.so.1': Permission denied ACCESS DENIED symlink: /usr/lib64/qt4/libqsa.so ln: creating symbolic link `libqsa.so': Permission denied >>> Completed installing qsa-1.2.1 into /var/tmp/portage/dev-libs/qsa-1.2.1/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-dev-libs_-_qsa-1.2.1-11323.log" symlink: /usr/lib64/qt4/libqsa.so.1.2.0 symlink: /usr/lib64/qt4/libqsa.so.1.2 symlink: /usr/lib64/qt4/libqsa.so.1 symlink: /usr/lib64/qt4/libqsa.so -------------------------------------------------------------------------------- !!! This ebuild is from an overlay: '/usr/local/portage'
(In reply to comment #0) > I have make and tested a new ebuild and all other necessary files to install > QSA 1.2.1 (dev-libs/qsa-1.2.1). > I have a problem. I install whit a overlay. but when a take emerge qsa I found this error. >>> Install qsa-1.2.1 into /var/tmp/portage/dev-libs/qsa-1.2.1/image/ category dev-libs ACCESS DENIED symlink: /usr/lib64/qt4/libqsa.so.1.2.0 ln: creating symbolic link `libqsa.so.1.2.0': Permission denied ACCESS DENIED symlink: /usr/lib64/qt4/libqsa.so.1.2 ln: creating symbolic link `libqsa.so.1.2': Permission denied ACCESS DENIED symlink: /usr/lib64/qt4/libqsa.so.1 ln: creating symbolic link `libqsa.so.1': Permission denied ACCESS DENIED symlink: /usr/lib64/qt4/libqsa.so ln: creating symbolic link `libqsa.so': Permission denied >>> Completed installing qsa-1.2.1 into /var/tmp/portage/dev-libs/qsa-1.2.1/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-dev-libs_-_qsa-1.2.1-11323.log" symlink: /usr/lib64/qt4/libqsa.so.1.2.0 symlink: /usr/lib64/qt4/libqsa.so.1.2 symlink: /usr/lib64/qt4/libqsa.so.1 symlink: /usr/lib64/qt4/libqsa.so -------------------------------------------------------------------------------- !!! This ebuild is from an overlay: '/usr/local/portage'
aaaa
Created attachment 132619 [details] Updated ebuild This one fixes sandbox bug
Closing as WONTFIX, as qsa-1.2 is for Qt4, and has been included in qt-4.3. Also available as x11-libs/qt-script for >=qt-4.4.
(In reply to comment #16) > Closing as WONTFIX, as qsa-1.2 is for Qt4, and has been included in qt-4.3. > Also available as x11-libs/qt-script for >=qt-4.4. No! qt-script and qsa are seperate packages. Just have a look at trolltechs ftp, you will see they released qsa-1.2.3 on Mai 15 2008, though qt-4.4.0 was released on Mai 02 2008. So why should they release a seperate product, that is just included in their main framework (qt-4.x) The classes offered with qsa are completely different from those coming with qt-script. qsa is an extension, offering special classes for scripting, such as an "extended editor for qt script" and so on. So please get the qsa-1.2 in portage, as it is really needed. Thx Franz
You're correct, it is a separate product, so we will add the latest version to portage. But you should be aware of: "First of all it is important to realize that Qt Script is only an interpreter, it does not provide an editor, completion or script project management, like QSA does. Qt Script however does provides almost full compliance with the ECMAScript standard and performs significantly better than the script engine provided by QSA." So for people who don't need the extras, qt-script is still the better choice. I noticed qsa-1.2.3 has been released in the meantime, so we should aim for an ebuild for that version to be added to portage. Thanks for reporting!
Created attachment 179907 [details] proposed ebuild. This is my proposal for 1.2.3 version. Needs more testing though . Please try this if you want and report possible issues so that we can fix it and put it in portage. Thanks :)
(In reply to comment #19) > Created an attachment (id=179907) [edit] > proposed ebuild. ebuild works for me. Thx!
I removed doc use flag cause it was really hard to modify all the makefiles to not build documentation. So this ebuild will install documentation anyway. But i preserved "examples" use flag to choose weather you want examples or not
Ok i ve pushed this ebuild on qting-edge overlay. Will stay there for now for futher testing and move it to the tree later ;)
The ebuild will stay in the overlay as long as Qt 4.4 is available in portage. This package does not work with Qt 4.5, which is already marked stable in portage. So we won't be adding this, unless a new release is made that does work with the current Qt version.
