Re: How to cope with patches sanely (Was: State of the project - input needed)

[Mike Hommey]

On Sun, Jan 27, 2008 at 02:25:49PM +0100, Magnus Holmgren wrote:
> On fredagen den 25 januari 2008, Mike Hommey wrote:
> > On Fri, Jan 25, 2008 at 09:55:02AM +0000, Jon Dowland 
> <[EMAIL PROTECTED]> wrote:
> > > On Fri, Jan 25, 2008 at 10:13:37AM +0100, Mike Hommey wrote:
> > > > The only sad thing is that quilt only deals with patches (i.e. diffs),
> > > > whereas dpatch can do scripts, too. Anyways, I now prefer not using
> > > > dpatch of quilt.
> > >
> > > Does anyone know how common it is for this additional functionality to
> > > be used in packages in the archive?
> >
> > I do use it for config.guess and config.sub update in package source tree,
> > though that can be done in debian/rules.
> 
> I consistently use /usr/share/doc/dpatch/examples/dpatch/01_config.dpatch.gz, 
> do you do that too?

I actually use a different approach:

#! /bin/sh -e
## 80_config.dpatch by Mike Hommey <[EMAIL PROTECTED]>
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: Use config.guess and config.sub from autotools-dev

AUTOCONF_DIRS="./build/autoconf/ ./directory/c-sdk/config/autoconf/"

dpatch_patch ()
{
        for dir in $AUTOCONF_DIRS; do
                for file in config.guess config.sub; do
                        sed -i '2!b;/^#/ i\exec "/usr/share/misc/'$file'" "$@"' 
$dir/$file
                done
        done
}

dpatch_unpatch ()
{
        for dir in $AUTOCONF_DIRS; do
                for file in config.guess config.sub; do
                        sed -i '2!b;/^exec "/ d' $dir/$file
                done
        done
}

DPATCH_LIB_NO_DEFAULT=1

. /usr/share/dpatch/dpatch.lib.sh


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]