Index | Thread | Search

From:
Stuart Henderson <stu@spacehopper.org>
Subject:
Re: [NEW] audio/ebook2cw
To:
Enzo Nicosia <me@katolaz.net>
Cc:
ports@openbsd.org
Date:
Wed, 10 Dec 2025 03:08:30 +0000

Download raw body.

Thread
now with actual attachment ;)

On 2025/12/10 03:08, Stuart Henderson wrote:
> On 2025/12/09 10:38, Enzo Nicosia wrote:
> > Hello,
> > 
> > ebook2cw is a command line program which converts a plain text ebook to
> > morse code MP3 or OGG files. It works on several platforms, including
> > Windows, Linux, FreeBSD and, finally, also OpenBSD.
> > 
> > It automatically splits and numbers the output files by chapters.
> > 
> > For a detailed description, please refer to the man-page or the project
> > website at https://fkurz.net/ham/ebook2cw.html
> > 
> > ebook2cw is distributed under GPLv2.
> > 
> > 
> > 
> > This is my first port, and I am willing to maintain it as I am using it
> > on a regular basis. I have patched the few remaining strcpy/strcat
> > warnings.  
> > 
> > I know that hamradio is not a top-level ports category, but this would
> > definitely belong also to the same category where ham-radio-related
> > ports like tlf or xlog live.
> > 
> > It has been tested on -current amd64, but it also builds and works fine
> > on 7.8 amd64. tar.gz attached.
> > 
> > Is this OK? Any feedback is more than welcome.
> > 
> > Thanks in advance
> > 
> > Enzo
> > 
> > -- 
> 
> 
> tweaked version attached;
> 
> - add a note to COMMENT for people that don't know CW == Morse code
> - CATEGORIES for amateur radio related ports is normally comms so use
>   that (not sure whether that or audio is best for the port dir)
> - more exact license marker
> - don't list library deps in BUILD_DEPENDS
> - break out deps to one line per dep
> - don't use "CONFIGURE_STYLE=none", it is meaningless
> - pass in DESTDIR via flags to avoid various patches
> - use INSTALL_STRIP rather than hardcoding -s (so that building with
>   "make DEBUG=-g" disables stripping)
> - drop DESCR paragraph about manpages and www (the URL is included
>   directly after in packages, so that should be fairly obvious, and
>   manpages are standard anyway
>