From owner-freebsd-ports@FreeBSD.ORG Sun Aug 17 15:13:39 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 9402F37B401 for ; Sun, 17 Aug 2003 15:13:39 -0700 (PDT) Received: from cultdeadsheep.org (charon.cultdeadsheep.org [80.65.226.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFFC643F75 for ; Sun, 17 Aug 2003 15:13:37 -0700 (PDT) (envelope-from sheepkiller@cultdeadsheep.org) Received: (qmail 7531 invoked from network); 17 Aug 2003 22:13:35 -0000 Received: from unknown (HELO lucifer.cultdeadsheep.org) (192.168.0.2) by goofy.cultdeadsheep.org with SMTP; 17 Aug 2003 22:13:35 -0000 Date: Mon, 18 Aug 2003 00:13:41 +0200 From: Clement Laforet To: Sergey Matveychuk Message-Id: <20030818001341.72b660ad.sheepkiller@cultdeadsheep.org> In-Reply-To: <3F3FF917.8040903@ciam.ru> References: <3F3FF917.8040903@ciam.ru> Organization: tH3 cUlt 0f tH3 d3@d sH33p X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386-portbld-freebsd5.1) X-Face: ._cVVRDn#-2((lnfi^P7CoD4htI$4+#G/G)!w|,}H5yK~%(3-C.JlEYbOjJGFwJkt*7N^%z jYeu[;}]}F"3}l5R'l"X0HbvT^D\Q&%deCo)MayY`);TO Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: ports@freebsd.org Subject: Re: RFC: patch for bsd.port.mk to use ${PORTSDIR}/MOVED 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: Sun, 17 Aug 2003 22:13:39 -0000 On Mon, 18 Aug 2003 01:52:23 +0400 Sergey Matveychuk wrote: > > It was primarily written to make a smooth migration from current 2 > > levels ports tree to a hypothetic 3 levels ports tree, > > Question 2 portmgr: is this planned? At least hypothetical :) It has been discussed many times, about twice a year ;-) And every time it's the same answer: "ports tree is growing we need this, it would be great" I don't know if it's planned, but I thought about it because I can't sleep. Keeping ports tree consistency, keeping categories backward compatibilty for packages system during ports migration, and after that, switching to news categories for packages can be one of the possible solutions. I have made some test. and It seems to work. The main migration may eat a lot of time (specially for orphaned ports) regards, clem