The py-metar package always fires up the "make config" dialog. How-To-Repeat: This sequence shows the problem: make config make rm -rf work make Notice that dialog starts up again and that any options changed earlier have reverted to their port defaults. I used ktrace/kdump and found that make is looking in two different directories for the options file: ktrace -di make kdump | fgrep NAMI | fgrep /var/db/ports 11049 make NAMI "/var/db/ports/metar/options" 11049 make NAMI "/var/db/ports/metar/options.local" 11049 make NAMI "/var/db/ports/metar/options" 11049 make NAMI "/var/db/ports/metar/options.local" 11049 make NAMI "/var/db/ports/py27-metar/options" 11069 make NAMI "/var/db/ports/metar/options" 11069 make NAMI "/var/db/ports/metar/options.local" 11069 make NAMI "/var/db/ports/metar/options" 11069 make NAMI "/var/db/ports/metar/options.local" 11069 make NAMI "/var/db/ports/py27-metar/options" 11085 mkdir NAMI "/var/db/ports" 11085 mkdir NAMI "/var/db/ports" 11085 mkdir NAMI "/var/db/ports/py27-metar" 11085 mkdir NAMI "/var/db/ports/py27-metar" I see other ports that set OPTIONSFILE but I'm not sure if the problem is with the OptionsNG in py-metar's Makefile or with OptionsNG itself.
Responsible Changed From-To: freebsd-ports-bugs->sunpoet Over to maintainer (via the GNATS Auto Assign Tool)
Hi Po-Chuan, would you commit/approve patch attached? It resolves the issue by adding OPTIONSFILE as original submitter suggests. Thanks. -- Regards, Ruslan Tinderboxing kills... the drives.
State Changed From-To: open->closed Committed, thank you!