Re: Some ports fail on -current because ${BINOWN} and ${BINGRP} seems to be not defined

2002-05-11 Thread Bill Fenner
This is presumably fallout from the /usr/share/mk rearrangement, but rev 1.306 of /usr/share/mk/bsd.port.mk should fix this. Oh, hey, are the failing ports all ones that use bsd.port.pre.mk and bsd.port.post.mk? I guess bsd.port.pre.mk needs the same fix as bsd.port.mk does. Bill To

Re: Some ports fail on -current because ${BINOWN} and ${BINGRP} seems to be not defined

2002-05-11 Thread Oliver Braun
* Bill Fenner [EMAIL PROTECTED] [2002-05-11 17:12]: This is presumably fallout from the /usr/share/mk rearrangement, but rev 1.306 of /usr/share/mk/bsd.port.mk should fix this. on my -current box it doesn't. The world was build last Saturday 2002-05-04, including rev 1.306 of

Some ports fail on -current because ${BINOWN} and ${BINGRP} seems to be not defined

2002-05-10 Thread Oliver Braun
Hi, I am currently checking bento's port building errors on -current. I have found some ports, e.g. audio/cam [1], that could not be installed because ${BINOWN} and ${BINGRP} seems to be not defined. They end up with the error: install: -g: Invalid argument coming from things like: