pkgsrc-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Portsentry 2.0 released



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

> 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


Home | Main Index | Thread Index | Old Index