[Pkg-zsh-devel] Differences between git repo and official tar balls: Are they still relevant?

Axel Beckert abe at debian.org
Mon Nov 30 02:04:36 UTC 2015


Hi,

now that pws started signing upstream tar balls and I implemented
verifying these signatures in
https://anonscm.debian.org/cgit/collab-maint/zsh.git/commit/?id=e6d23bf3
we should have a look if we still need to generate fake upstream tar
balls from git.

This is the current diff from our tar ball and the upstream one of the
current release candidate for 5.2:

→ tardiff ../zsh_5.1.1-test-3.orig.tar.xz ../zsh-5.1.1-test-3.tar.gz
+ Doc/Zsh/manmodmenu.yo
+ Doc/Zsh/modlist.yo
+ Doc/Zsh/modmenu.yo
+ Doc/help.txt
+ Doc/help/alias
+ Doc/help/bg
+ Doc/help/bindkey
+ Doc/help/break
+ Doc/help/builtin
+ Doc/help/cap
+ Doc/help/cd
+ Doc/help/clone
+ Doc/help/colon
+ Doc/help/command
+ Doc/help/comparguments
+ Doc/help/compcall
+ Doc/help/compctl
+ Doc/help/compdescribe
+ Doc/help/compfiles
+ Doc/help/compgroups
+ Doc/help/compquote
+ Doc/help/comptags
+ Doc/help/comptry
+ Doc/help/compvalues
+ Doc/help/continue
+ Doc/help/dirs
+ Doc/help/disable
+ Doc/help/disown
+ Doc/help/dot
+ Doc/help/echo
+ Doc/help/echotc
+ Doc/help/echoti
+ Doc/help/emulate
+ Doc/help/enable
+ Doc/help/eval
+ Doc/help/exec
+ Doc/help/exit
+ Doc/help/export
+ Doc/help/false
+ Doc/help/fc
+ Doc/help/fg
+ Doc/help/functions
+ Doc/help/getcap
+ Doc/help/getln
+ Doc/help/getopts
+ Doc/help/hash
+ Doc/help/jobs
+ Doc/help/kill
+ Doc/help/let
+ Doc/help/limit
+ Doc/help/log
+ Doc/help/noglob
+ Doc/help/popd
+ Doc/help/print
+ Doc/help/printf
+ Doc/help/pushd
+ Doc/help/pwd
+ Doc/help/read
+ Doc/help/return
+ Doc/help/sched
+ Doc/help/set
+ Doc/help/setcap
+ Doc/help/setopt
+ Doc/help/shift
+ Doc/help/source
+ Doc/help/stat
+ Doc/help/suspend
+ Doc/help/test
+ Doc/help/times
+ Doc/help/trap
+ Doc/help/true
+ Doc/help/ttyctl
+ Doc/help/typeset
+ Doc/help/ulimit
+ Doc/help/umask
+ Doc/help/unhash
+ Doc/help/unlimit
+ Doc/help/unset
+ Doc/help/unsetopt
+ Doc/help/vared
+ Doc/help/wait
+ Doc/help/whence
+ Doc/help/zcompile
+ Doc/help/zformat
+ Doc/help/zftp
+ Doc/help/zle
+ Doc/help/zmodload
+ Doc/help/zparseopts
+ Doc/help/zprof
+ Doc/help/zpty
+ Doc/help/zregexparse
+ Doc/help/zsocket
+ Doc/help/zstyle
+ Doc/help/ztcp
+ Doc/version.yo
+ Doc/zsh.1
+ Doc/zsh.texi
+ Doc/zshall.1
+ Doc/zshbuiltins.1
+ Doc/zshcalsys.1
+ Doc/zshcompctl.1
+ Doc/zshcompsys.1
+ Doc/zshcompwid.1
+ Doc/zshcontrib.1
+ Doc/zshexpn.1
+ Doc/zshmisc.1
+ Doc/zshmodules.1
+ Doc/zshoptions.1
+ Doc/zshparam.1
+ Doc/zshroadmap.1
+ Doc/zshtcpsys.1
+ Doc/zshzftpsys.1
+ Doc/zshzle.1
+ Etc/FAQ
+ META-FAQ
+ Src/patchlevel.h.release
- Util/difflog.pl
+ config.h.in
+ configure
+ stamp-h.in

So basically there are just tons of generated documentation files in
addition and Util/difflog.pl removed.

IMHO we should be able to move the generated files temporarily away
during the build (and copy them back afterwards), so they shouldn't
hurt us. And we don't use Util/difflog.pl so that shouldn't hurt
either.

The "configure" file is regenerate upon build anyways via
dh-autoreconf and we could handle *h.in like the generated
documentation and move them away temporarily.

What do you think?

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



More information about the Pkg-zsh-devel mailing list