Ben Bucksch wrote:
> What I need (on one hand) is the same as today: I need a fully
> functional Mozilla suite without crypto, i.e. where the US export law
> don't apply. However, I need to provide an add-on (with a small download
> size, today 1.2 MB or so), which makes this same build crypto-enabled.
> This makes it possible to use mirrors like Tucows*, which don't allow
> crypto, for distribution of the bulk of the app, and provide the crypto
> software as add-on from non-US mirrors.
By default, when you build mozilla you will *not* build PSM and NSS. By
setting an environment variable, when you build mozilla, PSM and NSS will
get built and installed into your mozilla bin directory.
To solve your problem, you can either generate two mozilla binaries (one
with no crypto and one with crypto enabled) or if you wish to upgrade a
mozilla installation that was not built with crypto enabled, you can
generate a PSM xpi package.
We will post more information on this in the next few days once we are close
to checking this in.
- David.
