On Thu, Feb 26, 2004 at 12:43:53AM +0000, Johnny C. Lam wrote:
> On Wed, Feb 25, 2004 at 10:49:46PM +0100, Manuel Bouyer wrote:
> > 
> > Index: bsd.pkg.mk
> > ===================================================================
> > RCS file: /cvsroot/pkgsrc/mk/bsd.pkg.mk,v
> > retrieving revision 1.1412
> > diff -u -r1.1412 bsd.pkg.mk
> > --- bsd.pkg.mk	25 Feb 2004 09:24:52 -0000	1.1412
> > +++ bsd.pkg.mk	25 Feb 2004 21:15:34 -0000
> > @@ -2487,7 +2487,7 @@
> >  			 ${ECHO} 'case $$pkgsrc_override in';		\
> >  			 ${ECHO} 'yes) exit 0 ;;';			\
> >  			 ${ECHO} 'esac';				\
> > -			 ${ECHO} ". ${WRKSRC}/$$file.overridden";	\
> > +			 ${ECHO} "${CONFIG_SHELL} ${WRKSRC}/$$file.overridden";	\
> >  			) > $$file;					\
> >  			${CHMOD} +x $$file;				\
> >  		fi;							\
> 
> The reason that the generated config.status file sources the overridden
> file instead of executing is is so that the overridden script can
> transparently use the same argument list.  If the above patch is applied,
> the overridden script will know it's called config.status.overridden and
> will be able to bypass config.status when calling --recheck.

Will config.status.overridden recall itself with --recheck ?
for kdelibs3 I didn't find in the script where it would do this.

>  Could you
> test the attached patch instead?

works for kdelibs3 and bison, at last.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--