-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Aug 4, 2007, at 1:30 AM, Lionel Elie Mamane wrote:
On Sat, Jul 21, 2007 at 04:25:07PM -0400, Barry Warsaw wrote:
I've just merged in my 'setuptools' branch to the official Mailman 3 branch.
Also gone are the C wrapper programs, so Mailman is now a pure Python application.
I suppose that means that all architecture-dependent code is gone?
Yes. I'm going to try very hard not to bring them back. I think we
can do that by using different mechanisms to integration Mailman with
mail and web servers, though I haven't worked my way high enough up
the stack yet.
All the packages Mailman depends on live in the Cheeseshop (...). And now that we're a setuptools-based project, when you build Mailman (see below), these dependent packages will be automatically downloaded and installed as necessary.
With the hat of distribution packager hat on, we will need a way to disable that mechanism. To be sure that our automated builds are self-contained and will _not_ access the network in any way. Is there any way to do that? I didn't find an option for that in "python2.5 setup.py --help".
Yes, but this is a larger issue than just Mailman because just about
any decent sized Python application your going to distribute these is
going to be built around this type of architecture. Probably the
same goes for Ruby and Perl but I don't know those language's
packaging systems very well.
I'm pretty certain eggs play well enough with various distribution
package management systems. I would start here for more information:
http://peak.telecommunity.com/DevCenter/setuptools
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRrR+W3EjvBPtnXfVAQJC1wP+MZ4zrVuFv4OrIC+4tb54s6ZFiOdrqAr9 EenGpf9pWG3Fgu4EnU1OXHK36vz4/SBv1kdoiUyxZ1l+6nE+wFzZ+uf4NekG4uV6 MqdHA3o/lJMfQ6ERpNPKEC9M3G2VzPkhgejAcYpU3ilTQhRbAJciADZ5jzruprZQ ZUnBQx+X9BI= =V/HV -----END PGP SIGNATURE-----