On Mon, Jan 26, 2026 at 08:32:49PM +0000, Stuart Henderson wrote: > libinotify is not a typical example because it installs to a non-standard > dir to try to avoid being picked up without explicit configuration in other > ports > > I've just looked through a bunch of libraries and struggling to find > something I'd suggest as a good starting point, many have something a bit > atypical - I'd start from ports/infrastructure/Makefile.template > > generally for a library we'd like to have some other software intended for > adding to ports that uses it, rather than just adding it standalone > > On 26 January 2026 18:47:12 "Sergey A. Osokin" <[email protected]> wrote: > > There're many libraries ported into OpenBSD available in > > the devel subdirectory of OpenBSD ports tree, > > https://cvsweb.openbsd.org/ports/devel/, and one of > > those is libinotify, so you may want to take a look on > > that here: > > - https://cvsweb.openbsd.org/ports/devel/libinotify/, or > > - https://github.com/openbsd/ports/tree/master/devel/libinotify/ > > > > It's also recommended to read OpenBSD Porter's Handbook, > > https://www.openbsd.org/faq/ports/index.html, describes > > porting, build, cleaning and other related staff for a port. > >
Thanks both! I'm starting with Makefile.template and looking at libinotify with caveats. :) -- Paul
