[ On Friday, April 2, 2004 at 21:27:35 (-0800), Jeremy C. Reed wrote: ]
> Subject: Re: INFO_DIR not used
>
> Can some others test this too?
> 
> Add to the .if defined(GNU_CONFIGURE) section in mk/bsd.pkg.mk:
> 
> +.  if !empty(INFO_FILES)
> +CONFIGURE_ARGS+=       --infodir=${PREFIX}/${INFO_DIR}
> +.  endif
> 
> (I have seen a few packages with troubles already, like editors/ed which
> has a very old configure script.)

I've been using the following for quite some time.  Note it allows for
turning off the options if the configure script is too old/broken to
support them.

+ .  if !defined(NO_CONFIGURE_INFODIR)
+ CONFIGURE_ARGS+=	--infodir=${GNU_CONFIGURE_PREFIX}/share/info
+ .  endif
+ .  if !defined(NO_CONFIGURE_MANDIR)
+ CONFIGURE_ARGS+=	--mandir=${GNU_CONFIGURE_PREFIX}/share/man
+ .  endif
+ # speeds up one-time builds, which is definitely pkgsrc!
+ CONFIGURE_ARGS+=	--disable-dependency-tracking

(oh, that last line's not exactly related :-)

So far I have only the following instances of NO_CONFIGURE_*:

	./devel/m4/Makefile:NO_CONFIGURE_INFODIR=	# defined
	./devel/m4/Makefile:NO_CONFIGURE_MANDIR=	# defined


(but keep in mind I don't do bulk builds -- I rarely install more than a
few hundred packages (228 currently on my main development system), and
I haven't ever tried GNU Ed since I already have a fine /bin/ed :-)

-- 
						Greg A. Woods

+1 416 218-0098                  VE3TCP            RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>          Secrets of the Weird <woods@weird.com>