hi! i just wrote an ebuild for the very nice visual Qt4 TikZ editor ktikz. it's still quite basic, doesn't have any useflags in it and for some reason the desktop menu icon gets installed twice. i guess a patch is needed to turn of automatic menu icon installation by `qmake && make && make install`. also, does anyone know in which ebuild the latex style preview.sty sits? it'd be needed to append this as depenceny, or at least tell the user at the end of the installation that he or she is supposed to install it. anyway, the ebuild works in terms of producing a usuable binary. comments, hints, improvements? cheers, nico Reproducible: Always
Created attachment 164620 [details] ktikz ebuild
Nice job, Nico. I've been meaning to create an ebuild for months, so this is very handy. On my system preview.sty is in dev-texlive/texlive-latexextra. I guess the rough-and-ready way of dealing with the surplus desktop menu icon is to remove it before installation.
Created attachment 171235 [details, diff] Patch for preview.sty and single desktop icon
hey alet, thanks for the comments. well i agree that plain removing the icon is the quickest fix, and i'm sure we can pull it in, too. it's not the nicest thing, though, i just poked the author of the package for installation options. same goes for the language files. i append another ebuild with your fixes, a spelling correction, and debug in IUSE (inherited from the qt4 class). cheers, nico
Created attachment 171240 [details] ebuild with fixes
oh, and by the way, what do you think about the category media-gfx?
I'm one of the autors of ktikz. Is there anything left I can do to make the packaging easier?
I tried to use the ktikz-06.ebuild for the new version 0.7 and got sandbox ACCESS DENIED errors. I could nor fix it since I have no skills in KDE development (do not know how to qmake works). Has anyone succeeded in building an ebuild for 0.7 yet?
hi christian, thanks for your notice. i just renamed the ebuild to ktikz-0.7, and it compiled just fine. i'm working on an amd64 here, having the things compiled by paludis (not emerge). you might want to try to remove the last line of the ebuild 'rm usr/...'. any luck with that? cheers, nico
hi florian, good to have you here! there is indeed something that you could help us with here. right now, when we build the application, we get two icons by default into the start menus. that's because the 'make install' procedure does it, and the gentoo package manager does it, too (in a clean way). now that i look at it, this might actually be the cause for christian's problems: ktikz tries to install something by default to /usr/share/applications, which very likely causes a sandbox violation. i'd be great to have some control over ktikz's installing the .desktop file. not sure how other at applications handle that (such as, for example, smplayer or say, firefox). same goes for installing translations. cheers, nico
Hello! > now that i look at it, this might actually be the cause for christian's > problems: ktikz tries to install something by default to > /usr/share/applications, which very likely causes a sandbox violation. This problem can be resolved by removing the corresponding lines from the qmake project file: sed -i -e '59,66d' src/src.pro (should be put somewhere before eqmake4 either in src_compile or src_unpack). Alternatively, you can write a patch that removes these lines. Once src.pro has been fixed, the "remove the extra desktop icon" part can be removed, too. BTW, where have the .qm files to be put so that the translation is actually used? BTW2, I used the bug report's ebuild for 0.6 to compile 0.7
I attached a 0.7 ebuild based on the previous version with the following two changes. 1. added the following line, as suggested, to avoid building the desktop icon > sed -i -e '59,66d' src/src.pro 2. required poppler-bindings to be built with the qt4 use flag > BTW2, I used the bug report's ebuild for 0.6 to compile 0.7 I built 0.7 but I assume my ebuild would work with 0.6 too.
Created attachment 172557 [details] updated ebuild (require poppler-bindings +qt4; don't build desktop icon)
Thanks for the initial ebuild. I made a couple of corrections and put it in the sunrise overlay since I'm not sure yet how much time I can spend on ebuild maintenance and how often I'm going to use ktikz. Please read more about the Gentoo Sunrise User Overlay here: http://overlays.gentoo.org/proj/sunrise/wiki You can take over the maintenance there if you want.
Hi, version 0.8 has been released, but doesn't build as find. Apparently, the package tries to manually install files where it's not supposed to. Hm... Cheers, Nico
Hi Nico, newest version is now 0.9. Unfortunately it fails to install for the same reason as 0.8. (Since version 0.7 is not very stable on my machine I wold like to upgrade, but I am not able too fix the Makefile to install into the sandbox)
> newest version is now 0.9. Unfortunately it fails to install for the same > reason as 0.8. (Since version 0.7 is not very stable on my machine I wold like > to upgrade, but I am not able too fix the Makefile to install into the sandbox) Most probably the sed command broke for 0.8. I updated and committed an ebuild for 0.9 to Sunrise. The following changes where made compared to the Sunrise ebuild for 0.7: - Added USE=kde for optional KDE4 support - Fixed dependencies to support >=poppler-0.10.6 - Fixed sed command to remove the correct lines - Added patch to fix KDE4 includes (reported to upstream) - Fixed sandbox violations during installation - General ebuild improvements (||die, quotations)
Hi Thomas, could you please update the ebuild to reflect the new dependencies, that is: farewell poppler-bindings (to be removed from tree anyway), hello poppler-qt4 (prolly virtual/poppler-qt4 then). Cheers, Nico
Hello Nico, > could you please update the ebuild to reflect the new dependencies, that is: > farewell poppler-bindings (to be removed from tree anyway), hello poppler-qt4 > (prolly virtual/poppler-qt4 then). I have read in a blog post by Ben de Groot that poppler packages will be reunited using USE dependencies, i.e. app-text/poppler will have a qt4 USE flag. http://ben.liveforge.org/2010/01/24/poppler-reunification Please clarify which dependency should be used for ktikz: - virtual/poppler[qt4] - app-text/poppler[qt4] - virtual/poppler-qt4 - dev-libs/poppler-qt4 Greetings, Thomas
Hi Thomas, > Please clarify which dependency should be used for ktikz: when I look at the virtual/poppler-qt4 it actually seems like this is nothing else than app-text/poppler[qt4] already (at least in the 0.12) branch. So, well, I guess it's safe to make it depend on virtual/poppler-qt4 now and when 0.10* has been removed to have it depend on virtual/poppler[qt4]. It compiles fine for me with dependency on virtual/poppler-qt4, *however ktikz would just segfault when trying to startup. Florian, any comments on that one? Cheers, Nico
Here's the traceback: ======================== *snip* ======================== Program received signal SIGSEGV, Segmentation fault. 0x00007ffff3e2a061 in strlen () from /lib/libc.so.6 #1 0x00007ffff5a167e3 in XSetCommand () from /usr/lib/libX11.so.6 #2 0x00007ffff5a1b1a9 in XSetWMProperties () from /usr/lib/libX11.so.6 #3 0x00007ffff705f387 in QWidgetPrivate::create_sys(unsigned long, bool, bool) () from /usr/lib/qt4/libQtGui.so.4 #4 0x00007ffff702ef6e in QWidget::create(unsigned long, bool, bool) () from /usr/lib/qt4/libQtGui.so.4 #5 0x00007ffff702bc1a in QWidgetPrivate::createWinId(unsigned long) () from /usr/lib/qt4/libQtGui.so.4 #6 0x00007ffff702bc1a in QWidgetPrivate::createWinId(unsigned long) () from /usr/lib/qt4/libQtGui.so.4 #7 0x00007ffff702ea7d in QWidgetPrivate::setWindowTitle_helper(QString const&) () from /usr/lib/qt4/libQtGui.so.4 #8 0x00007ffff702edcb in QWidget::setWindowTitle(QString const&) () from /usr/lib/qt4/libQtGui.so.4 #9 0x000000000043d36e in Ui_TemplateWidget::retranslateUi(QWidget*) () Current language: auto The current source language is "auto; currently asm". #10 0x000000000043d9e6 in Ui_TemplateWidget::setupUi(QWidget*) () #11 0x000000000043cfe9 in TemplateWidget::TemplateWidget(QWidget*) () #12 0x000000000044d3f1 in TikzEditorView::TikzEditorView(QWidget*) () #13 0x000000000043879f in MainWindow::MainWindow() () #14 0x000000000042c085 in KtikzApplication::init() () #15 0x000000000043015e in main () ======================== *snap* ======================== Cheers, Nico
Created attachment 227145 [details] ktikz 0.9 ebuild with poppler fixes Hi, despite the segfault here an ebuild with the latest fixes for the reworked poppler mechanisms. Cheers, Nico
Created attachment 275603 [details] Updatet ktikz ebuild for 0.10 Updatet ktikz ebuild for 0.10 using cmake to build with kde
Created attachment 341046 [details] ktikz ebuild with resolved qt dependencies New ebuild with updated dependencies: * replaced x11-libs/qt-gui:4 (not existing anymore) by dev-qt/qtgui:4 * added dev-qt/qthelp:4 because of required tool qcollectiongenerator Created binary is qtikz, ktikz is not compiled. I didn't investigate why, qtikz suffices for me.
Hello, everyone. It seems that at least one ebuild related to this bug exists in the Sunrise overlay at the moment. However, I have to regretfully announce that after a long inactivity period the Sunrise project has been discontinued and the related overlay will be eventually removed. For this reason, I'd like to ask you to reevaluate the ebuilds and consider moving them. If you'd like to maintain a package from Sunrise in Gentoo, please take a look at our Proxy Maintainers [1] project. Please make sure to take ebuilds from the unreviewed developer Sunrise repository [2] rather than the -reviewed one, since the latter has not been updated for over a year. While at it, please note that: 1. Adding a package to Gentoo requires declaring yourself as an active maintainer for it. All bugs regarding the package will be assigned to you, and you will be expected to maintain it. 2. Some packages may not be suitable for addition anymore. While there's no strong rules that would prevent you from adding a package, it may be a bad idea to add old-unmaintained packages that will shortly result in a large number of bugs reported with no solution. If that is the case, please close the bug as RESOLVED/OBSOLETE to make it easier to find packages worth adding. 3. Some of the bugs were already closed as WONTFIX/OBSOLETE/... while the relevant ebuild was kept in Sunrise. If you disagree with the original decision, you still can add the ebuild via proxy-maint. 4. Pleaes note that many of the Sunrise ebuilds are old and may be buggy. If you decide to move them, please make sure to update/clean them up. The proxy-maint team will also review your ebuilds, therefore making sure they land in Gentoo in good quality. Once again, thank you for your contribution. We hope that you will still want to contribute to Gentoo, through proxy-maint or otherwise. [1]:https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers [2]:https://gitweb.gentoo.org/proj/sunrise.git/
