> 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. I do think that per previous posts I have made, it would be most helpful to come up with a standard PEAR packaging policy that dealt with this and the other unique packaging issues which PEAR modules introduce. Charles -- Big blue tube It's a honey Best squeeze play For love Or money Burma-Shave http://burma-shave.org/jingles/1951/big_blue_tube
Attachment:
signature.asc
Description: Digital signature