Trimming bzr package size

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...
> make distclean
> cd ..
> tar -X $INFO_FILES -X $ELC_FILES -X $JUNK czf xemacs-src.tar.gz xemacs-$VERSION
> tar -X $JUNK czf xemacs-info.tar.gz $INFO_FILES
> tar -X $JUNK czf xemacs-elc.tar.gz $ELC_FILES
> tar -X $JUNK czf xemacs.tar.gz $TOPDIR
> 
> Works fine.  I don't do Windows, don't know how you'd do this for
> Windows (but that doesn't seem to be relevant here anyway).

Yeah. The windows standalone installer is about 13MB because we have to
include all of QT and python and PyQT, and Subversion libraries, and ...

If Windows had a decent dependency system, it would certainly be nice to
use it. :)

> 
>  > Though I also thought that part of building packages was to run the
>  > program's test suite, and I'm not sure how that works with ripping out
>  > the test suite...
> 
> Of course I do a build ("guaranteed to have built on the release
> engineer's host ... YMMV") and test.
> 
> You need to make sure the distclean target catches all test build
> products (including intermediate products that might fail to get
> cleaned up if a test crashes ... I know you'd *never* release if the
> test were failing, but somehow the penultimate mess seems to get
> grandfathered into the ultimate release, with red faces all around).
> 
> I'm pretty sure that there must be standard ways of doing all this in
> debhelper, if Ubuntu uses that.
> 
> 

It does, though I don't know all the tricks and issues involved. I also
know the current release process uses "bzr-builddeb" to automate a
couple of the steps. Though I would guess that is mostly calling out to
debhelper/dch/etc.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkouiB0ACgkQJdeBCYSNAANVcwCfXRMvQs7xd41jKVYC+b8Epo4W
SScAoJcSF73mv7jyVSjwYPIWV9mfTYZo
=x8Wh
-----END PGP SIGNATURE-----