Re: What to do when new version available upstream...
On Sat, 27 Feb 1999, Josip Rodin wrote:
> 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).
>
> BTW rename upstream_src.tgz to aspell_0.27.orig.tar.gz so that it gets
> recognized by dpkg-buildpackage automatically.
>
> > 3. dh_make and try to build?
>
> dh_make should IMHO be used only for new packagings. When you already
> have a good debian/* and others, why start again with default files?
Indeed. Don't use dh_make for an upgrade.
Jules
/----------------+-------------------------------+---------------------\
| Jelibean aka | jules@jellybean.co.uk | 6 Evelyn Rd |
| Jules aka | jules@debian.org | Richmond, Surrey |
| Julian Bean | jmlb2@hermes.cam.ac.uk | TW9 2TF *UK* |
+----------------+-------------------------------+---------------------+
| War doesn't demonstrate who's right... just who's left. |
| When privacy is outlawed... only the outlaws have privacy. |
\----------------------------------------------------------------------/
Reply to: