On Thu, Jun 30, 2005 at 03:26:05PM +0200, Piotr Roszatycki wrote:
> drwxr-xr-x dexter/dexter 0 2005-06-30 15:23:06 php-db-1.7.6.orig/
> -rw-r--r-- dexter/dexter 124807 2005-06-30 15:23:06
> php-db-1.7.6.orig/DB-1.7.6.tgz
>
> So *.orig.tar.gz contains really original archive with the same md5 hash as
> PEAR package. The update from upstream is easy - in fact I need to run `pear
> download DB' in the new `php-db-1.7.7.orig' directory if DB-1.7.7 will
> appear.
>
> What do you think?
so i'm not too familiar with this method of packaging, but it seems
fairly reasonable to do what you want -- that is to keep the debian
changes outside of the tarball, so you don't have to manually muck
with new upstream tarballs at all most of the time. i'm personally a
recent convert to the dpatch+svn+svn-buildpackage combo[1], but this is
merely personal preference.
sean
--
[1] i track my ./debian dirs in svn, use dpatch to track all changes,
keep upstream tarballs in a parent directory, and svn-buildpackage
automatically assembles everything for me.
Attachment:
signature.asc
Description: Digital signature