Re: local patches feature

["Dan Kegel" <dank at kegel dot com>]

On 2/19/06, Robert P. J. Day <rpjday@mindspring.com> wrote:
> > You should also consider to use a quilt like patch stack mechanism ...
>
> all i did for my mini-script was have a PATCH_DIRS variable which is
> set to the default of the current patch directory, but which you could
> append other directories to, and the patches would be added in that
> order.  i didn't try to get any fancier than that, so it was
> essentially a shell script loop wrapped around the normal patch
> processing.
>
> is there (at least for now) any need for it to be more complicated
> than that?

Simple is better for the moment.
In fact, I'd kind of prefer there just be a SITE_PATCH_DIR
variable; if set, getandpatch.sh would check there, too.  e.g.
instead of

    if test -d $TOP_DIR/patches/$BASENAME; then

we'd have
   for patchdir in $TOP_DIR/patches $SITE_PATCH_DIR; do
       if test -d $patchdir/$BASENAME; then
- Dan

--
Wine for Windows ISVs: http://kegel.com/wine/isv

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.org