Subject: Re: how can we create PATCHFILES that are not DISTFILES?
To: NetBSD Packages Technical Discussion List <tech-pkg@netbsd.org>
From: Greg A. Woods <woods@weird.com>
List: tech-pkg
Date: 04/19/2002 13:17:36
[ On Friday, April 19, 2002 at 12:12:44 (-0400), Andrew Brown wrote: ]
> Subject: Re: how can we create PATCHFILES that are not DISTFILES?
>
> >I've been trying to update a pkgsrc module and I've run into a situation
> >where the best way to enable an option seems to be to optionally patch
> >the source before building, using a specific patch selected from a set
> >of multiple optional patches (included in say ${FILESDIR}), based on
> >some setting in mk/bsd.prefs.mk and/or /etc/mk.conf.
> 
> make your patch contain all features, and then enable each feature
> based on the presence of some preprocessor token.  ie, if you have a
> patch that does something for alpha machines, your patch would contain
> code surrounded by #ifdef alpha/#endif.

What are you talking about?

There's no invocation of cpp in the data path between the patch file and
the patch program.  Are you proposing one?

-- 
								Greg A. Woods

+1 416 218-0098;  <gwoods@acm.org>;  <g.a.woods@ieee.org>;  <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>