[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: tarball in tarball: opinions



On lördagen den 5 juli 2008, Jay Berkenbilt wrote:
>  * I like to have an exact copy of the downloaded source tarball with
>    the same md5 checksum, gpg detached signature, etc.  Using the
>    rules/tarball.mk from cdbs provides a very convenient way of
>    handling this.

The .orig.tar.gz is supposed to be that exact copy. What prevents you from 
letting it be that? (Besides upstream providing only a .tar.bz2 (but that 
will be supported with the 3.0 format) or .zip.)

>  * I manage my debian directories in subversion, and I use
>    svn-buildpackage to build.  I always use "mergeWithUpstream".
>    Sometimes I want to do something more involved, so I just manually
>    extract my .orig.tar.gz files.  I can't do this without tarball in
>    tarball if my packages either contain their own debian director
>    that I don't use or if they extract to a directory other than
>    pkg-version.

Upstream tarballs containing debian directories are the exception, and should 
be discouraged, but with the 3.0 (quilt) format they will be ignored anyway. 
Tarballs using the wrong top-level directory name is nothing that can't be 
worked around. You can always use svn-buildpackage --svn-export.

-- 
Magnus Holmgren        holmgren@debian.org
Debian Developer 

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: