Re: Portsentry 2.0 released

[Marcus Hufvudsson <mh%protohuf.com@localhost>]

On 6/24/25 11:15, Thomas Klausner wrote:
> On Tue, Jun 24, 2025 at 11:11:47AM +0200, Marcus Hufvudsson wrote:
> > Hi! Thanks for the quick reply and WIP to repackage Portsentry!
> >
> > Regarding your patch: I believe you have downloaded the 2.0.2 release.
> Actually the last tagged release as of this morning, 2.0.1
>
> https://wip.pkgsrc.org/cgi-bin/gitweb.cgi?p=pkgsrc-wip.git;a=blob;f=portsentry/Makefile;h=62bbd7e96c13858cb614b8391519713559062b6b;hb=37b62aa9cb265f079868fae815a1c147a69c001d

Silly me, I meant 2.0.1. I'm working on releasing 2.0.2 ;)

For some reason I couldn't access portsentry on pkgsrc-wip. The URL 
above returns:

ERR_CONNECTION_REFUSED

I also tried: pkgsrc.se, but I can't find portsentry in WIP there.


> > This
> > issue has been addressed in the master branch (but is currently unreleased).
> > The CMakeLists.txt now uses the "GNUInstallDirs" supported by CMake, it
> > looks like this:
> >
> > --- snip --
> >
> > include(GNUInstallDirs)
> >
> > install(TARGETS portsentry DESTINATION ${CMAKE_INSTALL_SBINDIR})
> >
> > install(FILES examples/portsentry.conf DESTINATION
> > ${CMAKE_INSTALL_SYSCONFDIR}/portsentry)
> >
> > ...
> >
> > --- snip --
> >
> >
> > Here's the full current version for your review:
> > https://github.com/portsentry/portsentry/blob/master/CMakeLists.txt
> >
> > I realize NetBSD might not adhere to the GNU way in terms of paths, but I
> > think it would be possible for your package system to override these paths
> > or something? Let me know if this is something you can work with or if we
> > need to come up with some alternative way to handle path resolution in
> > NetBSD.
> This is fine, no problem.
>
> > If this works for you, I could make an official 2.0.3 release in case you
> > want a stable upstream reference in your package.
> Whenever you're ready for that, the patch is fine in the meantime.
>
> Did you see anything that should be changed in the package?
>
> Thanks,
>   Thomas