From owner-freebsd-ports Sat Sep 8 13:15:23 2001 Delivered-To: freebsd-ports@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id 5D2BB37B40B for ; Sat, 8 Sep 2001 13:15:19 -0700 (PDT) Received: from athlon.pn.xcllnt.net (athlon.pn.xcllnt.net [192.168.4.3]) by kayak.xcllnt.net (8.11.4/8.11.4) with ESMTP id f88KFIf26282 for ; Sat, 8 Sep 2001 13:15:18 -0700 (PDT) (envelope-from marcel@kayak.pn.xcllnt.net) Received: (from marcel@localhost) by athlon.pn.xcllnt.net (8.11.6/8.11.5) id f88KFI001422 for ports@FreeBSD.org; Sat, 8 Sep 2001 13:15:18 -0700 (PDT) (envelope-from marcel) Date: Sat, 8 Sep 2001 13:15:18 -0700 From: Marcel Moolenaar To: ports@FreeBSD.org Subject: linux_base: update in place or repo copy? Message-ID: <20010908131518.A1238@athlon.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.21i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Gang, We have a choice to make. I can not update the current linux_base port in place without breaking a large portion of the current linux_base depending ports. We did that for 6.1 and there have been times I wished we didn't. OTOH, creating a linux_base-7, as I then like it to be called, has its disadvantages too. it's possible to track RH 7.x with it I assume, but what happens if RH 8.x is released. The choices are: 1. We do not upgrade at all, 2. We upgrade in place and live with any breakages it causes and do our best to resolve whatever needs to be resolved as quickly as possible, 3. We "branch-off" and create a seperate port so that people have a choice which one they want to install. Maintainers can update their oown ports iat their leisure, 4. Other; explain. thanks, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message