Long-standing portupgrade vs. make config issue

[Randy Pratt]

On Thu, 8 Jun 2006 12:35:42 -0400
Garance A Drosihn <drosih at rpi.edu> wrote:

> I have never been prompted twice for a given set of
> options.  I do, at times, get prompted for the options
> of one port, answer that screen and walk away, only to
> later see that I was also prompted for the options of
> some other port.

I got tired of these silent screens and added an audible sound
warning to /usr/ports/Mk/bsd.port.mk :

--- Mk/bsd.port.mk.original   Mon May 29 22:04:13 2006
+++ Mk/bsd.port.mk   Mon May 29 22:06:06 2006
@@ -5281,6 +5281,7 @@
      shift 3; \
   done; \
   TMPOPTIONSFILE=$$(mktemp -t portoptions); \
+  /usr/local/bin/play /home/rpratt/sounds/montymes.wav; \
   trap "${RM} -f $${TMPOPTIONSFILE}; exit 1" 1 2 3 5 10 13 15; \
   ${SH} -c "${DIALOG} --checklist \"Options for ${PKGNAME:C/-([^-]+)$/
\1/}\" 21 70 15 $${DEFOPTIONS} 2> $${TMPOPTIONSFILE}"; \
   status=$$?; \

It has to be patched each time the ports tree is cvsupped and it
may not be the best place to do it but it seems to work (for me).

It could be much better written with a call to an external script
with more options and eliminate hard-coded values.  It probably
causes ozone depletion and other scary things.  YMMV.

I'm almost sure something like this will never get officially added
since its probably considered bloat.  At least I'm not wasting
hours of build time not knowing I need to push a button.

Randy


--