Subject: Re: CVS commit: pkgsrc/mk
To: Roland Illig <>
From: Stoned Elipot <>
List: pkgsrc-changes
Date: 11/02/2005 09:20:32
Now if GNU_CONFIGURE_INFODIR is set but INFO_DIR is not set in sync
the "automatic" info files handling in PLIST and installation/deinstallation
migh be broken. I would prefer that GNU_CONFIGURE_INFODIR to be removed,
and only left INFO_DIR as the knob to set the installation path
for info files, relative to GNU_CONFIGURE_PREFIX of course.

Cheers, Stoned.

On Mon, Oct 31, 2005 at 09:12:29PM +0100, Roland Illig wrote:
> Jeremy C. Reed wrote:
> >On Mon, 31 Oct 2005, Roland Illig wrote:
> >
> >>Log Message:
> >>Added two new variables, GNU_CONFIGURE_INFODIR and GNU_CONFIGURE_MANDIR.
> >>Up to now, a package that wanted to use a different location for
> >>--mandir had to first define CONFIGURE_HAS_MANDIR=no and then
> >>CONFIGURE_ARGS+=--mandir=${...}, which looks weird. Now it only has to
> >
> >How many packages need this? (I didn't count.)
> devel/cmake
> graphics/gocr
> That makes two packages. I haven't looked yet through a whole bulk build 
> (not an incremental one) to detect all those broken packages, but I 
> expect about five more that would benefit from this change.
> >It seems like if a GNU_CONFIGURE (uses autoconf) package use --mandir in 
> >its own way, then it is broken. Maybe we should just fix the few 
> >packages to correctly use --mandir.
> If you want to dive into the various hand-written files and 
> fix them, you may do that. I prefer just setting one variable that has 
> the same effect.
> Roland