Date: Sun, 10 Feb 2013 05:10:02 GMT From: John Hein <jhein@symmetricom.com> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/175621: update net/dhcpcd Message-ID: <201302100510.r1A5A2lx037911@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/175621; it has been noted by GNATS.
From: John Hein <jhein@symmetricom.com>
To: Raphael Kubo da Costa <rakuco@FreeBSD.org>
Cc: <bug-followup@FreeBSD.org>, Roy Marples <roy@marples.name>
Subject: Re: ports/175621: update net/dhcpcd
Date: Sat, 9 Feb 2013 22:01:17 -0700
Raphael Kubo da Costa wrote at 22:55 +0200 on Feb 3, 2013:
> Is the CONFIGURE_ARGS line really necessary? bsd.port.mk already passes
> `--mandir=${MANPREFIX}/man' by default.
That is only added to CONFIGURE_ARGS if configure --help | grep --
--mandir returns a positive result.
However, the configure script that is included in the current dhcpcd
distribution does not. It's not a autoconf generated configure
script. But it's close (and I want other things that GNU_CONFIGURE in
bsd.port.mk provides, such as --prefix and --build for cross builds,
etc.). We could just as well use HAS_CONFIGURE instead of
GNU_CONFIGURE and provide --prefix, etc., manually in addition to
--mandir. But I chose to use GNU_CONFIGURE and add --mandir manually.
We could add a comment explaining it since it's a bit abnormal...
# current configure script won't trigger the bits in bsd.port.mk to add
# --mandir, so do it manually here
CONFIGURE_ARGS+= --mandir=${PREFIX}/man
No response from maintainer now for a couple weeks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201302100510.r1A5A2lx037911>