Re: What to do when new version available upstream...
Jules Bean <firstname.lastname@example.org> writes:
> > On Wed, Feb 24, 1999 at 11:57:02AM -0800, Sudhakar Chandrasekharan wrote:
> > > 1. tar zxvf upstream_src.tgz
> > > 2. Apply the .diff that was generated when I produced 0.26.2 (and get rid
> > > of the files like changelog, control etc.)
> > I usually extract the new one (or apply a patch if that is the method),
> > gunzip -dc old_version.diff.gz > somefile, then edit that 'somefile' and
> > replace all instances of progdirectory-1.2.0 with progdirectory-1.2.1.
> > Then apply that new diff with patch -p0 < somefile. And then clean up the
> > .rej and .orig files and apply the missing stuff manually.
> The editing isn't necessary.
> Simply patch -p1 < somefile and it will ignore the first directory
> component (the versioned directory).
I never had the guts to do that. What happens if the upstream author heavily modifed
a file that is modified in your diff? I guess patch is supposed
to be smart, but is this failsafe?
John Lapeyre <email@example.com>