I have tested sthen's edited version of textproc/sword on amd64 hardware 
in -current. Clean and working -- as expected.

It seems to me that it is time to add this long-awaited port to our 
tree. Will you do the honors, Mr. Henderson?

Corey

Corey Stephan, Ph.D.
coreystephan.com

P.S.

Thank you for taking the time to explain these intricacies to me, sthen. 
I always appreciate your clear habit of welcoming newcomers to these 
lists with thoughtful, targeted messages. Basically, if I see that a 
message is from sthen, then I know that it is going to be helpful. This 
met that expectation. Cheers.

On 4/23/23 01:33, Stuart Henderson wrote:

> here are some fixes on top. new tgz attached,
> 
> - https homepage/master sites
> 
> - fix shared library versioning
> 
> - more specific license marker
> 
> - add missing deps, remove unzip which is handled by ports
> 
>    autoconf picks up clucene. it appears the software doesn't
>    use it if xapian is detected, nevertheless it is still linked.
>    it would be better to fix the build infrastructure to avoid
>    linking in that case. i have not done that.
> 
> - set wantlib, compiler (required for c++ ports)
> 
> - rather than replacing -lstdc++ with -lc++, don't specify it,
>    the c++ linker takes care of this and -lc++ won't work if built
>    with gcc (e.g. sparc64)
> 
> - use @sample, don't tell the user to copy sword.conf.
>    setting SWORD_PATH seems unnecessary, isn't that what sword.conf
>    is for?
> 
> - information about who wrote the port belongs in commit log rather
>    than DESCR
> 
> - remove rcs id-like string from plist - we don't use these any more
>    (and when we did it doesn't work with a different keyword)
> 

Reply via email to