On 2025/04/23 00:02, Hugo Osvaldo Barrera wrote:
> On question (all other comments are clear)…
> 
> On 2025-04-22 17:35, Stuart Henderson wrote:
> > On 2025/04/22 17:58, Hugo Osvaldo Barrera wrote:
> > […]
> > > +pre-build:
> > > +	sed \
> > > +		-e 's@OPENBSD ?= no@OPENBSD = yes@' \
> > > +		-e 's@CONFIGFILE = .*@CONFIGFILE = /etc/owntracks-recorder.conf@' \
> > > +		-e 's@DOCROOT = .*@DOCROOT = /var/www/owntracks-recorder@' \
> > > +		-e 's@STORAGEDEFAULT = .*@STORAGEDEFAULT = /var/db/owntracks-recorder@' \
> > > +		${WRKDIST}/config.mk.in \
> > > +		> ${WRKDIST}/config.mk
> > 
> > use a patch instead of this sed substitution
> 
> I'm piping the output of send into a new file here. Should I use a patch
> to create this new file, or include that the config.mk in the ports
> repo?

I would probably cp it in post-extract and then patch. The problem with
seds like this is that it's difficult to spot when they get out-of-sync
after an update.