From owner-freebsd-gnome@FreeBSD.ORG Tue Jan 4 09:49:12 2005 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80F6F16A4CE for ; Tue, 4 Jan 2005 09:49:12 +0000 (GMT) Received: from 212.106.254.141.adsl.jazztel.es (212.106.254.141.adsl.jazztel.es [212.106.254.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A88443D31 for ; Tue, 4 Jan 2005 09:49:11 +0000 (GMT) (envelope-from josemi@freebsd.jazztel.es) Received: from [192.168.254.16] (orion.redesjm.local [192.168.254.16]) j049n9Ek000875 for ; Tue, 4 Jan 2005 10:49:10 +0100 (CET) (envelope-from freebsd@redesjm.local) Message-ID: <41DA6695.2020904@redesjm.local> Date: Tue, 04 Jan 2005 10:49:09 +0100 From: Jose M Rodriguez User-Agent: Mozilla Thunderbird 1.0 (X11/20041227) X-Accept-Language: en-us, en MIME-Version: 1.0 To: gnome@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.5; VDF: 6.29.0.31; host: antares.redesjm.local) Subject: Proposition for new mozilla ports X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 09:49:12 -0000 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