From owner-freebsd-ports@FreeBSD.ORG Thu Jan 15 06:45:24 2009 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18F0A106564A for ; Thu, 15 Jan 2009 06:45:24 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with ESMTP id 9BF0A8FC2B for ; Thu, 15 Jan 2009 06:45:23 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 3238 invoked by uid 399); 15 Jan 2009 06:45:23 -0000 Received: from localhost (HELO ?192.168.0.4?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 15 Jan 2009 06:45:23 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <496EDB80.4020908@FreeBSD.org> Date: Wed, 14 Jan 2009 22:45:20 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Ion-Mihai Tetcu References: <20090114203941.7516d639@it.buh.tecnik93.com> <496E62F8.6080103@FreeBSD.org> <20090115084013.268c7be5@it.buh.tecnik93.com> In-Reply-To: <20090115084013.268c7be5@it.buh.tecnik93.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org Subject: Re: portmaster some_port vs. portmaster 'some_port*' X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2009 06:45:24 -0000 Ion-Mihai Tetcu wrote: > On Wed, 14 Jan 2009 14:11:04 -0800 > Doug Barton wrote: >> When portmaster gets multiple ports on the command line (whether via a >> glob or via a list) the initial portmaster process acts like a task >> scheduler. The parent spawns new portmaster processes for each >> individual port and keeps track of the various issues such as >> dependencies already updated, etc. When all the ports listed have been >> updated the parent cleans up the temp files and exits. > > Hmm, then can you please document this explicitly in the man page? > > From my point of view it should also check the dependency relation > between whatever it gets after parsing the command line ( N ports, M > ports as a result of a wild-card, ...). The dependency checking happens as a natural result of the normal upgrade process of each port. The only thing different in the "multi-port" case is that for each dependency a given port's portmaster process checks if that dependency is otherwise up to date but is on the list of multi-ports, it is marked for upgrade anyway. > Else I'm afraid it is a nice way to self-foot-shooting. I'm afraid that I don't see what problem you're concerned about. If you could state your concern more clearly I can try to address it. Meanwhile if you can reproduce something, let me know. Regards, Doug -- This .signature sanitized for your protection