I noticed that while we have nice builds for sword, and bibletime (KDE) in the app-text category, we were missing an ebuild for gnomesword. I have therefore tried to create an ebuild for bibletime. This ebuild is dependant on Sword, gtkhtml, gnome-print and gdk-pixbuf. The program will build against ispell or aspell if they are found. I was not certain if this needed a DEPEND or RDEPEND, so I didn't put one in. The patch is to fix a bug that filed the source in '/usr/doc/gnomesword' instead of 'usr/share/doc/gnomesword-0.7.8'. It also fixes an issue where a define wasn't being set so the build would crash. There was probably a different way of doing this, but I couldn't find it. Thank you.
Created attachment 7633 [details] gnomesword-0.7.8.ebuild (new ebuild)
Created attachment 7634 [details, diff] Small patches for gnome-sword to keep directory standards and force a #define
I would love to see this ebuild become a part of the normal distribution!
a bit of patience please, we're kinad lagging behind on ebuilds with our small team. A few tidbits about this ebuild which could probably cleaned up : 1. the keywords, if you didnt test a certain arch, dont put it in. If you deliver an ebuild for x86 always mark it as ~, since your testing isn't enough to mark it stable. 2. I think there should at least be gtk/gnome-libs or something depends, i don't think the app can run without it. 3. try to use 'einstall' and 'econf' if possible
There's a new version (0.79) out now.
thnx for the notification, i will try to look at it in the next few days.
FYI - gnome2 port is been started (depends on sword-1.5.6 (cvs))
Hello, I have created the ebuild for 0.7.9. I'll attach the files now. Martin
Created attachment 16181 [details] The ebuild file for gnomesowrd-0.7.9
Created attachment 16182 [details] The gnomesword-0.7.9.gentoo.patch
Charles, you wrote they are working on a gnome2 release, do you have a link for that? Martin
Thanks for the 0.7.9 ebuild... still learning how to do that. I found out about the gnome 2 build while looking around the gnomesword cvs http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/gnomesword/gnomesword2/
*** Bug 36615 has been marked as a duplicate of this bug. ***
Since a new version is expected out soon, I'll take this bug (reassign it to me if you want) and maintain the package next release, as many new features are already in gnomesword's cvs.
i'm fine with you maintaining it, but at this point i want it to work reliable first before it goes in. So that means i'll go over the ebuild first before it enters the tree, i'll hand maintenance over from when that is done.
0.7.9 is now obsoleted both by 2.0.0 and 0.7.10. Currently building 2.0.0 with GNOME 2.6 (I also have the CVS sources to hand to check for differences) - will report back once I've got things working, if this actually happens...
Okay, well it appears that 2.0.0 needs some fairly serious work. I'll see what I can do. The deps in the duplicate bug mentioned above are all over the place, and FHS compliance is... well... actually it isn't. Also, we need a IUSE="spell" and fixes for the compile errors. I don't think I'm going to bed tonight :-P
The configure script automagically checks for gnome-spell. One thing you could do is have optional aspell support: local myconf if [ `use spell` ] ; then myconf="${myconf} --enable-use_aspell" fi ./autogen.sh ${myconf} Note however that I am having trouble getting gnomesword to build correctly with errors such as: distcc[8046] ERROR: compile on localhost failed bibletext_dialog.c: In function `create_nav_toolbar': bibletext_dialog.c:747: warning: assignment makes pointer from integer without a cast bibletext_dialog.c:758: error: invalid type argument of `->' make[3]: *** [bibletext_dialog.o] Error 1
I've had millions of those. Also there's a heavy amount of usage of previously deprecated and now with GTK+ 2.4 non-existent functions. Unfortunately, I'm not going to have time to complete the 2.0.0 port. That said, the first CVS update for 4 months happened today, so maybe the package's author has restarted work on this... I certainly hope so! I'm trying instead to emerge gnomesword-0.7.10 now. If I get millions of errors with that, I'm going to give up.
the 'myconf' stuff is sort of deprecated. You should be using 'use_enable'. You should'nt be running autogen there btw, it should not be needed with properly packaged tarballs. The gtk deprecation breakage should be easy to workaround, see bug #45747 for examples .
Okay, cheers for that foser, I'll have a go and see what I can come up with. autogen.sh is required for gnomesword2-cvs (obviously) but not gnomesword-0.7.10 or gnomesword2-2.0.0. With a bit of coaxing, gnomesword-0.7.10 copmiles and installs fine (the 0.7.9.gentoo patch needs fixing) but it would obviously be nicer to get gnomesword2-2.0.0 going, as 0.7.10 is the only reason I now have GNOME 1 libraries on my system.
Okay, well I'm actually getting segfaults all over the place with 0.7.10. I could see if I could fix it, but I can't be bothered, it's a waste of effort - I'm going to see what I can do with 2.0.0.
Created attachment 29630 [details] app-text/gnomesword-2.0.1_pre1 ebuild Please test this ebuild.
I'll test that... as soon as you can tell me why there's a gtkhtml-1.1 dep in there? It's unnecessary, as it can use libgtkhtml-3.x instead (3.0 I think) which is neater, as that's part of GNOME 2 rather than GNOME 1. I'm currently testing with the dep on >=libgtkhtml-3.0. I'll report back as soon as I get anywhere.
Okay, just to confirm - the gtkhtml dep should be libgtkhtml-3.0, not gtkhtml-1.1. Aside from that, this works like a charm. Great work, thanks! :-D
I emerged sword 1.5.7, the latest version of sword-modules and tried the2.0.1 pre1 ebuild. Despite giving lot of warning messages, it appears to build fine. However, whenever I enter gnomesword2 from gnome terminal I get a "segmentation fault" error (no more, no less). Trying to start using the menus give the same result. Not sure if this helps, but I'm using GCC 3.3.3. I would love to get this working so any suggestion would be helpful.
Try re-emergeing sword and gnomesword with CFLAGS="-O0" CXXFLAGS="-O0". I haven't found another solution yet.
Thanks Robert. It worked perfectly. And thanks, Jon, for the ebuild. Much appreciated.
Compiled and installed great here. The only error I get is: (gnomesword2:7970): GnomeUI-WARNING **: Could not find GNOME pixmap file /usr/local/share/pixmaps/gnomesword/dlg-un.pn FWIW: I contacted the publishers of the NIV, NASB, and KNJV and still none of them are willing to release the NIV, NKJV, or NASB. Pleasant responses from them, but it unfortunate that we have to wait a while longer before they become public domain.
GnomeSWORD-2.0.1_pre1 segfaults when compiled with GCC 3.4.0. I've been rebuilding repeatedly using whatever version of gcc-3.4.0 I have installed at the moment, and it's just recently started working again. However, I'm using CVS for SWORD and GnomeSWORD. Because of the dependency issues I've also got a modified ebuild for sword-modules. They're available here: http://home.jesus.ox.ac.uk/~rmoss/portage/local/app-text/ If anyone wants to investigate and dig out the relevant fix(es), feel free...
alright, working sword and bibletime ebuilds are now in portage. Sadly, I had to do a cvs snapshot, and then the gcc devs went and made a version of gcc stable that broke everything :(. Also, I think gnomesword is on the verge of a new release- there is much activity on the mailing list. Before committing any ebuilds from here, I'd like to make sure they work with the very-new version of sword which is now in portage. BTW, thanks Rob for helping out with the gcc-3.4 porting- it turned out to be a sword problem :).
Created attachment 34884 [details] app-text/gnomesword-2.0.1_pre1 ebuild sorry, this is not compatible with newer versions of sword, so it looks like the wait to add it will be even longer. For those wanting to do work on it, here is the latest proposed ebuild for when it does come out.
Jon, I can't test this right now, but you want to pass "--enable-sword_cvs" to configure. Otherwise, you'll get things crapping out. That actually negates the need for that patch I made, but I only just found this out. The reason for this is that the sword developers haven't made a new release of sword for quite a while. Once they do that and we're able to bump 1.5.8_pre1 to 1.5.8 proper, the need for this option will be removed. Once I get my computer back up - some time tonight or tomorrow, it's sat in the car waiting for me to unpack it at the moment - I'll see if I can scare this into working. In the meantime, if you want to beat me to it and get this updated and tested, I'm quite happy for you to do that...
Created attachment 34887 [details] app-text/gnomesword-2.0.1_pre1 ebuild Hey, there we go, it did work, thanks Rob! Ooo, it's nice, too. I can't wait until the gnome gives us the thumbs-up sign to add this to portage.
Well good luck with that one Jon - I hope and pray that this happens at some point in the next, oooh, year :-P BTW - it's great, isn't it?! And even stable. Mmmmm, stability...
What do you mean by stable? I get: Calculating dependencies ...done! >>> emerge (1 of 1) app-text/gnomesword-2.0.1_pre1 to / >>> md5 src_uri ;-) gnomesword-2.0.1_pre1.tar.bz2 >>> Unpacking source... >>> Unpacking gnomesword-2.0.1_pre1.tar.bz2 to /var/tmp/portage/gnomesword-2.0.1_pre1/work >>> Source unpacked. /usr/sbin/ebuild.sh: line 33: ./autogen.sh: No such file or directory !!! ERROR: app-text/gnomesword-2.0.1_pre1 failed. !!! Function src_compile, Line 33, Exitcode 127 !!! (no error message) Martin
looks like one of the bad tarballs I had on the site for a while- rm /usr/portage/distfiles/gnomesword-2.0.1_pre1.tar.bz2, redigest, and try again.
Created attachment 35616 [details] app-text/gnomesword-2.1.1.ebuild I would very much like to maintain this in portage, if I can get the gnome herd's ok on this? I already maintain the sword-related programs, so this would be very easy for me to keep up with. Just give me the nod or assign it to me :). 2.1.1 is very nice and should be included!
Jon, the ebuild should probably use the gnome2 eclass. Is it a gtk1 or gtk2 application or both? I'll have a closer look at the dependencies, but adapt the ebuild to use the gnome2 eclass first, just take a look at some of the samples in gnome-extra/ Thanks
Created attachment 37371 [details] gnomesword-2.1.1.ebuild Is there a particular category the gnome herd would like this to be in? It is a gtk2 app.
nope.. i guess something like app-{misc,text} or something should be the right place 2.1.1 still is a dev release, i'm not sure it's wise to use it (iirc the stable release didn't work so well either..) @ebuild : *libgkthtml dep prolly need fixing, are you positive it works with libgkthtml-3.1 as well (implied now) * gal & gdk-pixbuf deps are prolly incorrect * gnome-print idem dito *intltool is a runtime dep * you rely on spell autodetection now, isn't there a hard configure switch ?
Now in portage with suggested changes. The dependencies in the ebuild are the ones defined in the README and INSTALL files. Thanks gnome herd :).
then those are wrong (probably not updated)... anyway you should really start taking your deps from the configure script
