Hi Yaroslav, On Fri, Oct 19, 2007 at 10:27:49AM -0400, Yaroslav Halchenko wrote: > > > occasionally and I want to preserve orig.tar.gz files, so it is > > > better to keep them separately in ../tarballs for instance. So gbp > > > just needs to check (if there is no orig in build-area already) if > > > there is such in ../tarballs (or some other configurable directory) > > I wonder if this is really necessary - generating the tarball from the > > upstream-branch should work too. What's the real difference over > > storing it in the filesystem? > Well -- the point is that I (and I know lots of others ;-)) do not want > to generate upstream tarball since most of the time I have upstream > tarball which I got from upstream webpage and which can be easily > verified by any paranoid user to be unaltered tarball but simply > comparing md5/sha-sum of it to the tarball which could be found on upstream > page. Hmm...you can drop it into ../build-area (or whereever you build) then? Do you want to keep it in an extra place to be able to do a rm -rf build-area/? I'd rather not add an extra parameter to store upstream tarballs since keeping it in git by itself looks like a much nicer way to me - integrating pristine-tar support looks like a much nicer option. Would that suit your needs? Cheers, -- Guido
signature.asc
Description: Digital signature
