Created attachment 219801 [details] nunllmailer-pkg-plist-patch Attached is a modernized pkg-plist file for mail/nullmailer - use @postexec not @preexec commands - use @rmtry instead of @postunexec rm -f
Build and package info is available at https://gitlab.com/swills/freebsd-ports/pipelines/244064573
Uffe: Thanks for the patch. As this port currently doesn't have a maintainer, do you want to maintain this port?
Hello, Actually I was the maintainer of nullmailer for a number of years. But as stated in a response to a similar question in PR 251074 - the amount of validation requirements for ports have risen to a pile that big - that I'm not really in the mood for being a maintainer anymore... :-/
(In reply to Uffe Jakobsen from comment #3) Yeah, there are many tools for validating the ports now to help developers and contributors. Indeed, the drawback is this sometimes confusing people who are not familiar or don't have enough resource on hand. I believe this is necessary for raising the ports quality, but we also need to have modern tools to help us to complete the work. After all, good tools should help people, not demotivate people. I took sometime today to fix a project I started a while ago - using Cirrus CI to test FreeBSD ports. I made an example for mail/nullmailer and test this patch: https://github.com/lwhsu/freebsd-ports-nullmailer/pull/1 Please feel free to use this (I can even transfer this repository to you), help this can help you regain some motivation to maintain a port you care. Also feel free to ask me any question about this, this is still a WIP, but it is good enough for testing ports like libreoffice: https://github.com/freebsd/freebsd-ports-libreoffice . We will definitely provide more tools and services to help port maintainers.
@lwhsu are you still working on committing this patch?
(In reply to Robert Clausecker from comment #5) Not right now, but I think I can try to squeeze time to continue on it (and help is welcomed). I was mainly hoping to encourage Uffe to maintain the ports.
If you are not working on committing the patch, you should perhaps unassign this PR from yourself so others know that you are not working on it. The patch has been in limbo for two years because you assigned it to yourself despite having no intent to commit it.
(In reply to Robert Clausecker from comment #7) Yes I should and sorry that I forgot it, I should revise the list more often. I was waiting the response from Uffe and then forgot about it.