Proposition for new mozilla ports

[Jose M Rodriguez]

Well, after my latest round on firefox/mozilla/thunderbird, I found real 
advance, but a lot of problems to resolve.

In the way to take this, I think that this port structure and workplan 
must be of interest for mozilla ports evolution under gnome@

First, at last here, and to maintain 'official builds' on the tree while 
going, actual firefox/mozilla/thunderbird ports must be repro-copy in 
devel versions, and flaged as not distributable or packaged.

For the structure of the future ports (repro-copied for devel version), 
this must be taken in accont

 Our consideration about build 'official' or 'comunity' builds must be 
mainly for the FreeBSD official package build cluster, and must be in 
effect when building with PACKAGE_BUILDING defined and no options.

In any case, non-devel ports must be, at last, 'on the line' of 
'comunity' builds.  We may try new ideas on -devel, ask mozilla@ if 
convenient, and then merge on mainstream ports.

In the case we go on the line of 'comunity' builds for mainstream 
packages (I think this must be convenient, FreeBSD needs may or may not 
be the same as mozilla foundation), mainstream ports must obey a global 
defined MOZILLA_BRANDING env and do official builds.

This will maintain open a upstream comunication with mozilla foundation, 
and may have official FreeBSD packages in mozilla foundation CDroms, 
build in a special run in a package build cluster with  MOZILLA_BRANDING 
defined.

Also, to fullfill this, may be of interest having some support for 
external localized build (not langpacks), mainly for mozilla barnding 
and CDRoms.

For license arrangement, maintreams ports must adapt his comments and 
use pkg-suffix to fullfill 'comunity' builds, and only revert to offcial 
ones if PACKAGE_BUILDING (if go offcial) or MOZILLA_BRANDING is defined.

Any comments on this are welcome
--
  josemi