From owner-freebsd-ports@FreeBSD.ORG Wed Oct 15 12:40:46 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9391D16A4B3; Wed, 15 Oct 2003 12:40:46 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8BCA43FBF; Wed, 15 Oct 2003 12:40:42 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (localhost [127.0.0.1]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h9FJegbe000951; Wed, 15 Oct 2003 12:40:42 -0700 (PDT) (envelope-from marcel@ns1.xcllnt.net) Received: (from marcel@localhost) by ns1.xcllnt.net (8.12.9/8.12.9/Submit) id h9FJegCT000950; Wed, 15 Oct 2003 12:40:42 -0700 (PDT) (envelope-from marcel) Date: Wed, 15 Oct 2003 12:40:42 -0700 From: Marcel Moolenaar To: Joe Marcus Clarke Message-ID: <20031015194042.GA781@ns1.xcllnt.net> References: <1066241563.721.27.camel@gyros> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1066241563.721.27.camel@gyros> User-Agent: Mutt/1.5.4i cc: FreeBSD GNOME Users cc: ports@freebsd.org Subject: Re: RFC: What to do with Mozilla X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 19:40:46 -0000 On Wed, Oct 15, 2003 at 02:12:44PM -0400, Joe Marcus Clarke wrote: > As some of you may be aware, Mozilla 1.5 was released today (along with > Firebird and Thunderbird updates which will be handled soon). The > question is, what do we do with Mozilla 1.4.x? Do you resurrect > mozilla-vendor to hold 1.4.x for a while, or do we just update > www/mozilla to 1.5, and say "to hell" with 1.4.x? Note, 1.6a is due out > shortly as well, and mozilla-devel will be updated to that. I would suggest to resurrect mozilla-vendor for as long as it takes bento to iterate over all the ports. That way you have a trivial band-aid "fix" in case something does break. If nothing breaks, then mozilla-vendor can be put in the attic again after having lived for as short as a couple of days. If something did break then it lives for as long as it takes to fix the breakage. The name (ie mozilla-vendor) does not have to match common parctice or does not have to be intuitive. The port is not created to be used. it's created as a safety-net. You might as well call it mozilla-oops. My $0.02 -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net