On Thu, Jun 30, 2005 at 03:26:05PM +0200, Piotr Roszatycki wrote: > Hi. > > I wonder how original PEAR packages should be repackaged into *.orig.tar.gz. > In fact there is no original package anymore so it shouldn't be contains > "orig". Another thing: there is no easy way to produce the newer "orig" > archive so uupdate won't work. > > My proposition is to package i.e. DB-1.7.6.tgz into php-db_1.7.6_orig.tar.gz: > > 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? When I created my dh-make-php scripts for pecl and pear I had similar thoughts, but finally decided to take the original pear/pecl package, unpack in, move it to php[4]-(pearname|peclname)-version e.g. ps-1.3.1 -> php4-ps-1.3.1 and copy the package.xml file into that directory. This slightly modified directory is what I called .orig.tar.gz although it is not quite right. Updating through uupdate isn't possible unless uupdate can be customized somehow and take a different approach for an update. Uwe -- MMK GmbH, Universitaetsstr. 11, 58097 Hagen Uwe.Steinmann@mmk-hagen.de Tel: +2331 840446 Fax: +2331 843920
Attachment:
signature.asc
Description: Digital signature