From owner-freebsd-hubs Fri Dec 15 02:28:18 1995 Return-Path: owner-hubs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA11604 for hubs-outgoing; Fri, 15 Dec 1995 02:28:18 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA11596 for ; Fri, 15 Dec 1995 02:28:09 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.3/8.6.9) id CAA02725; Fri, 15 Dec 1995 02:28:01 -0800 (PST) Date: Fri, 15 Dec 1995 02:28:01 -0800 (PST) Message-Id: <199512151028.CAA02725@silvia.HIP.Berkeley.EDU> To: rkw@dataplex.net CC: hubs@freebsd.org In-reply-to: (rkw@dataplex.net) Subject: Re: 2.1R/ports and ports-2.1 on ftp.freebsd.org From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-hubs@freebsd.org Precedence: bulk * Actually, it needs to be changed anyway. * The 2.1.0-RELEASE/ports directories should be FROZEN at the value they had * at release time. * the ports-2.1 entry can then be a tree of symbolic links for those elements * that are unchanged. But if something changes, it should appear in ports-2.1 * but not 2.1.0-RELEASE/ports. However, we (the ports team) are not planning to maintain the 2.1 ports tree any further. We simply do not have the manpower to maintain two trees. So, any new change will go to FreeBSD-current/ports, which may or may not work with 2.1. (Actually most of them should work, except for ones that depend on newer bsd.port.mk or something.) Satoshi