On Thu, Jun 30, 2005 at 02:17:46PM -0400, Charles Fry wrote: > > 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? > > I am against the inclusion of the original archive in the *.orig.tar.gz. > > Of the other options I have seen used, my preference is to simply copy > (or rename) the original archive to *.orig.tar.gz. The problem is, that the pear/pecl package .tgz file contains a directory <name>-<version>, which is fine, but a package.xml file outside of this directory, which should be better inside. In my approach package.xml is simply copied into the directory and the result is the .orig.tar.gz, though I'm not sure if this is the right way to go. Uwe -- MMK GmbH, Universitaetsstr. 11, 58097 Hagen Uwe.Steinmann@mmk-hagen.de Tel: +2331 840446 Fax: +2331 843920
Attachment:
signature.asc
Description: Digital signature