Documented list of packages needed for release?

John Arbash Meinel john at arbash-meinel.com
Thu Mar 19 20:43:19 GMT 2009


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

Bob Tanner wrote:
> AsI work through building releases, I've noticed some holes in the
> releasing documentation.
> 
> I'm looking to fill those holes in. Currently, I would like to document
> all the packages necessary -and- optional for getting a release built
> and tested.
> 
> In no particular order (looking for verification on this list as well):
> 
> - docutil
> - pycrypto
> - pyrex
> - medusa
> 
> Others?
> 
> -- 
> Bob Tanner <tanner at real-time.com>                 | Phone : 952-943-8700
> http://www.real-time.com, Linux, OSX, VMware | Fax      : 952-943-8500
> Key fingerprint = F785 DDFC CF94 7CE8 AA87 3A9D 3895 26F1 0DDB E378
> 

In doc/developers/ppa.txt I'll note that it lists some more packages
that you need for building a .deb:
    sudo apt-get install build-essential devscripts dput quilt patch
          libcrypt-ssleay-perl debhelper cdbs python-docutils

It is probably "python-pyrex", "python-crypto", "python-medusa". Also
for 2.6 we are going to be using "pyftplib" now that Vincent's patch has
landed. I don't know if that code is packaged for Debian/Ubuntu yet or
not. (medusa hasn't been updated in a while, and is incompatible with
python2.6)

python-paramiko is something you need for sftp support

You'll need something like "build-essential" to get gcc et all.

I'm not really sure what else.

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

iEYEARECAAYFAknCrmcACgkQJdeBCYSNAANGIgCcChH3zzI2zXgiV4aOIJN6VjKS
JtoAn1N68kTyCQMZgDEb1/mLRjGmpNYW
=zzJb
-----END PGP SIGNATURE-----



More information about the bazaar mailing list