Thank you very much, gentlemen, for your generous work to bring this port to completion.
For the record and posterity, here are two small closing notes (nothing about changing the port, since it is done): I. Code Stability >> - use upstream' version number for KJV, should the hash change it'd >> be easier to fix the port. > > good idea. if it's changing fairly often then it's probably better to > mirror somewhere but we can figure that out later if needed. Yes, that makes sense. Yet, I ought to clarify that both SWORD and the KJV module that we are including with the OpenBSD port (as a ubiquitous sample) are highly stable, if not frozen or past development. Now that we have SWORD in the tree, it is likely that the port only ever will have to be adjusted to account for changes to OpenBSD's tooling -- not for changes to SWORD. Active development relating to the SWORD project is happening on making new modules (translations, lexica, commentaries, extensions, etc.) and front-end interfaces, not SWORD itself. II. Using SWORD on OpenBSD As I wrote in my initial message, I hope to bring BibleTime (Qt5), Xiphos (GTK), or both upstream from Aprendiendo de Jesus (adJ) in the (near) future so that we can have a clean front-end interface on-hand. Others may/should look into compiling BibleTime and/or Xipos themselves and/or bringing here to ports@ before me: https://gitlab.com/pasosdeJesus/adJ/-/tree/main/arboldes/usr/ports/mystuff/textproc At this moment, I cannot get BibleTime to build, despite it having straightforward build and run-time dependencies (all in-tree, now that we have textproc/sword) *and* me having it working without issue a few weeks ago. The error log is odd, but I trust that I will get it sorted. Xiphos, on the other hand, requires at least 3 'mystuff' ports as dependencies from downstream adJ (gtkhtml4, glib2, and biblesync). Without a fully featured front-end, I do not currently know of an *automatic* way to install modules. Modules may, however, be installed *manually* without hassle by downloading them from a Web browser or even a simple FTP connection. Both are possible, for example, from the official CrossWire repository: https://www.crosswire.org/sword/modules/index.jsp Ultimately, modules belong in /usr/local/share/sword/modules or ~/.sword/modules Anyway, turning back to the interface question, we do have at least two immediate options: 1) Bible Desktop Aside from module downloading (see above), the CrossWire Bible Society's official, (extremely) simple Java GUI for SWORD works out-of-the-box on OpenBSD. For example: a) Download the Bible Desktop Unix image: https://www.crosswire.org/bibledesktop/download.html b) 'unzip' & 'export JAVA_HOME=/usr/local/jdk-17/' c) 'cd bibledesktop-*' & './BibleDesktop.sh' 2) diatheke SWORD comes with the diatheke CLI. For more information, see https://wiki.crosswire.org/Frontends:Diatheke or, with textproc/sword installed, simply type 'diatheke --help' --- Deus vos benedicat, Corey Stephan, Ph.D. coreystephan.com
