From owner-freebsd-ports@FreeBSD.ORG Tue May 25 02:57:19 2004 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 0A92B16A4CE for ; Tue, 25 May 2004 02:57:19 -0700 (PDT) Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4218C43D49 for ; Tue, 25 May 2004 02:57:18 -0700 (PDT) (envelope-from Alexander@Leidinger.net) Received: from fwd07.aul.t-online.de by mailout06.sul.t-online.com with smtp id 1BSYgM-0005H2-02; Tue, 25 May 2004 11:57:14 +0200 Received: from Andro-Beta.Leidinger.net (EXXmhsZJQezA78WG1i2lh8GJbwzCZGNHQutUHC+clhGLzdgzpy6o8A@[84.128.200.146]) by fmrl07.sul.t-online.com with esmtp id 1BSYfw-0kR43k0; Tue, 25 May 2004 11:56:48 +0200 Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) i4P9uvqg044146; Tue, 25 May 2004 11:56:57 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Date: Tue, 25 May 2004 11:58:10 +0200 From: Alexander Leidinger To: Garance A Drosihn Message-Id: <20040525115810.2e2af232@Magellan.Leidinger.net> In-Reply-To: References: <20040524193815.21b18d80@Magellan.Leidinger.net> X-Mailer: Sylpheed version 0.9.10claws (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Seen: false X-ID: EXXmhsZJQezA78WG1i2lh8GJbwzCZGNHQutUHC+clhGLzdgzpy6o8A@t-dialin.net cc: freebsd-ports@freebsd.org Subject: Re: Third "RFC" on on pkg-data ideas for ports 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: Tue, 25 May 2004 09:57:19 -0000 On Mon, 24 May 2004 17:47:34 -0400 Garance A Drosihn wrote: > At 3:46 PM -0400 5/24/04, Garance A Drosihn wrote: > >At 7:38 PM +0200 5/24/04, Alexander Leidinger wrote: > >> > >>ATM you can checkout one (new/updated) port from cvs into > >>any non-"ports/" directory and it will work just fine > >>(depending on the dependencies of the port). I don't see > >>how this is possible with [the above] approach. > > > >..., I was assuming > >that the end-user would still be working in a copy of the > >entire ports-collection, so I was just going to download > >into ports/Packages. Maybe that isn't the right idea. > > Actually, the solution is probably pretty simple. Just > create a distfiles/Patches directory, and download any > missing "ports-collection patches" into that directory, > if we can't find them in ports/Patches... In this case get rid of ports/Patches and have all patches automatically downloaded, no need to have more than one such directory. But this will add "trash", since there's no automatic way to remove downloaded patches which are outdated (I play a little bit with your point of saving space here). You can remove some at the fetch-patches stage (and you have to, to not have some outdated ones in a new build), but you would have to issue a "make fetch-patches" for every port the user ever touched to clean everything up. I don't know how important this issue is for our user base, I just tell you about some issues which cross my mind and you have to decide on your own about them. Bye, Alexander. -- I'm available to get hired (preferred in .lu). http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7