Please find updated ebuild for sword-1.5.4. This updates bug #8845. Enjoy! Pat
Created attachment 4706 [details] sword-1.5.4.ebuild (Updated Package)
Created attachment 4713 [details] sword-1.5.4.ebuild (Updated Package to fix LDPATH) This updated ebuild fixes the LDPATH put into /etc/env.d/99sword-1 . It was /usr/lib/sword-1 which isn't created, and is now /usr/sword/1/lib which is what IS created.
It's good to get this package into gentoo... i know everytime I tried to install it on debian unstable it would never go right... /usr/sword/1/lib is NOT a good location... /usr/lib/sword-1 is more correct. I will get the ebuild working correctly so things follow FHS standards.
Thanks for clarification on the FHS standard. The bibletime ebuild (bug #8846) will also need to be updated to point to the correct lib location.
just curious why you chose the /var/db/sword to put the modules into? someone on the bt-devel list mentioned /usr/share/sword might be a good place for the modules. thoughts?
/var/db/sword ... I thought this might be a better place since the modules do not change the behavior of the library, like a software plug in, and there are user preference. Most of the reason is because MySQL puts databases into /var/lib/mysql. I realize this data changes as MySQL is running, but to me it made since for the sword modules as well.
*** Bug 8845 has been marked as a duplicate of this bug. ***
I stayed with default install locations determined by econf and things lay out very nicely. (/usr/share/sword for the datadir) It has been setup under app- text/sword. Please test and let me know if things work properly. bibletime (homepage appears to be down) and gnomesword will be added to portage soon.
Thanks. Couple of questions: 1) What did you opt to set the SLOT to 0 ? Looking to a future sword version 2 (or perhaps even 1.6, 1.7, etc.) we could use the slot to prevent upgrading from breaking current apps. So SLOT could be SLOT="1" or SLOT="1.5". 2) Where's the standard documentation, such as README, etc. ? Also you'll notice in the ebuild I submitted I included the developer's documentation as well for those who wish to developer using sword. (I realize my ebuild uses /var/db/sword instead of /usr/share/sword, but I think /usr/share/sword is better after all, should be a minor change in my ebuild).
I believe that sword depends on zlib by default, to handle compressed modules. Should there be a second dependancy of "sys-libs/zlib" ? I was initially skeptical myself about the extra docs that Pat included, but actually I think he's right, they should be included. Nice to see this package included in portage! AJ
I'll add the docs today.
added some docs and html api documentation.
I opted to slot 0 because there are no conflicting packages currently. For the future, we can put things in /usr/share/sword2 if really need be but I don't forsee any filesystem layout issues with the release of sword v2. All pertinent documentation has been added now including the examples and samples which I missed from your ebuild. I think I got everything now. :) Thanks for the submission! Keep em coming! :)
Sounds good, thanks. For future reference (as I do plan to submit more ebuilds), what is the general policy for assigning slots? The developer howto simply says it can be done and use the SLOT variable, but doesn't define the circumstances in which to do so, nor the prefered layout.
It works with my bibletime ebuild. I modified the bibletime ebuild to not specify the sword directories and it found them all. Currently I only use sword with bibletime so that's all I have to test.
